64-bit

问题 We had an assignment where we had to write the collatz conjecture in 64bit nasm assembly with only 13 commands or less (RET included). Now we are wondering how much you can actually reduce it. We are currently on 9. Heres the collatz conjecture in pseudo code for reference: Heres the code we have so far. A few notes: A tutor of us said we can remove the XOR rax, rax because of some calling convention it's already zero. It doesn't work on my computer though so I've included it here. I'm aware

问题 I'm running Delphi XE on Windows 7 Pro 64 and IIS 7.5, developing an ISAPI application. IIS is configured correctly (including allowing 32-bit code to run in an ISAPI process). The ISAPI process runs properly. In Delphi I'm trying to attach to the ISAPI process running on localHost to step through my ISAPI.dll code: Run->Attach to Process->InetInfo.exe. I've done this a thousand times with Windows XP and IIS 5, but in this new environment I cannot attach to the ISAPI process. I get an error

问题 I'm using GDB to debug code that was assembled with nasm -felf64 -Fdwarf when I want to examine the value at a label symbol, say var_h: dq -1 using print var_h GDB assumes that the value is 32-bit and only gives me the lowest 4 bytes x \1gx $var_h gives an error along the lines of "cannot convert value to integer' Very grateful for any ideas! 回答1: This should work: (gdb) x/gx &var_h Your other commands, as well as "along the lines of ..." make no sense. Details matter , and you should always

问题 I'm doing some legacy work with Python 2.7.18 in 64 bit. When PIP calling the compiler (VC for Python), it erroneously refer to 32-bit (x86) sources looking for include files, for example "-IC:\Program Files (x86)\MySQL\MySQL Connector C 6.0.2\include" . For 32-bit everything works all OK; for 64-bit the pre-compiled wheel file is an alternative that I prefer not to use for now. I'm wondering did I miss any setting pointing python and its compiler to 64-bit instead of x86? Or, at lease I want

问题 In my visual studio 2010 ultimate, codes in #if _WIN64 region is always dark. I selected X64 platform in my configuration manager. What do I do to compile a 64 bit project? 来源： https://stackoverflow.com/questions/18862945/how-to-build-a-64-bit-project-in-visual-studio

问题 In my visual studio 2010 ultimate, codes in #if _WIN64 region is always dark. I selected X64 platform in my configuration manager. What do I do to compile a 64 bit project? 来源： https://stackoverflow.com/questions/18862945/how-to-build-a-64-bit-project-in-visual-studio

问题 When I run cmake-gui and hit configure, I can specify the generator for my project. I can choose Visual Studio solution, Eclipse, makefiles etc... I am on 64bit system and want to build 64bit application. Till now, I used Visual Studio 10 Win64 generator to generate my solutions. No I want to (have to) build it with makefiles. But there is no options 32b/64b. Are makefiles for 64bit build used by default (on 64b system) and for 32b only after using something like export CFLAGS=-m32 inside my

问题 Can I use the assembly routines for Serpent encryption in the link below written for 32-bit x86 from a 64-bit program on an x86-64 machine? That is, without launching a separate 32-bit process for it? If not, does anyone have a pointer to an optimized implementation of Serpent that works in both 32 and 64 bit (LGPL is OK but cannot use GPL since it's a commercial project)? http://gladman.plushost.co.uk/oldsite/cryptography_technology/serpent/serpent.asm 回答1: You will need to convert the

问题 Can I use the assembly routines for Serpent encryption in the link below written for 32-bit x86 from a 64-bit program on an x86-64 machine? That is, without launching a separate 32-bit process for it? If not, does anyone have a pointer to an optimized implementation of Serpent that works in both 32 and 64 bit (LGPL is OK but cannot use GPL since it's a commercial project)? http://gladman.plushost.co.uk/oldsite/cryptography_technology/serpent/serpent.asm 回答1: You will need to convert the

问题 Problem description I try to get code working under 64-Bit VBA which works fine in 32-Bit VBA. It is regarding Common Controls TaskDialogs. I use Microsoft Access, but the problem should be the same in other VBA hosts. One part works fine in both (32- and 64-Bit) VBA, the other part doesn't. TaskDialog API working well in both (32- and 64-Bit) VBA You can start the procedure TestTaskDlg for a test. Option Explicit 'Original API definition: '------------------------ 'HRESULT TaskDialog( ' HWND