64-bit

问题 We use msbuild to build our .NET application on a server dedicated to builds. We are migrating to new hardware which has 64 bit Windows 2003. I can build the application using the 64 bit version of msbuild found in Framework64 or I can build it using the 32 bit verison found in Framework. Is there any advantage to building with the 64 bit version of msbuild? 回答1: Not particularly no. The only real advantage is that the 64 bit version of msbuild will be able to take advantage of more address

问题 In the header file WinUser.h , there is a part in which the constants of the second parameter of SetWindowLong() are defined. // ... #define GWL_WNDPROC (-4) #define GWL_HINSTANCE (-6) #define GWL_HWNDPARENT (-8) #define GWL_STYLE (-16) #define GWL_EXSTYLE (-20) #define GWL_USERDATA (-21) #define GWL_ID (-12) #ifdef _WIN64 #undef GWL_WNDPROC #undef GWL_HINSTANCE #undef GWL_HWNDPARENT #undef GWL_USERDATA #endif /* _WIN64 */ #define GWLP_WNDPROC (-4) #define GWLP_HINSTANCE (-6) #define GWLP

问题 I'd confidently say 99% of applications we write don't need to address more than 2Gb of memory. Of course, there's a lot of obvious benefit to the OS running 64-bit to address more RAM, but is there any particular reason a typical application would be compiled 64bit? 回答1: There are performance improvements that might see with 64-bit. A good example is that some parameters in function calls are passed via registers (less things to push on the stack). Edit I looked up some of my old notes from

问题 I'm looking for strategies and articles on making Carbon code 64-bit ready. Carbon for 64-bit does not and will not exist. It's pretty much a dead end. So in order to bring Carbon application and toolkits to 64-bit their GUI part will have to be re-written in Cocoa and Objective-C, right? How can I minimize the effort I have to put into the transition? How can I minimize the amount of needed Objective-C code? 回答1: So in order to bring Carbon application and toolkits to 64-bit their GUI part

问题 I've read a bit about compressed object pointers in some 64 bits Java VM implementations. As I understood it, the principle is storing a reference as a relative 32 bits address offset from one object to another instead of a full 64 bits pointer, to gain memory. I believe that this kind of optimization is not currently applied to the .NET CLR. At least I couldn't find anything about it. Could it be potentially applied to it or would that be an impossible/useless/performance-degrading

问题 I found a nice piece of code here that executes ASM instructions using API calls in order to obtain the serial number of the CPU: using System; using System.Text; using System.Runtime.InteropServices; namespace ConsoleApplication1 { class Program { [DllImport("user32", EntryPoint = "CallWindowProcW", CharSet = CharSet.Unicode, SetLastError = true, ExactSpelling = true)] private static extern IntPtr ExecuteNativeCode([In] byte[] bytes, IntPtr hWnd, int msg, [In, Out] byte[] wParam, IntPtr

问题 Our workstations are running 64-bit Vista, and the production servers for our ASP.NET MVC web apps are 64-bit Server 2008 servers. However, our build server running TeamCity is a Server 2008 32-bit server. We will taking these builds and deploying them on the 64-bit production servers. The applications are written all in C#. Should I be concerned about doing the builds in a 32-bit environment? Is it necessary to upgrade our build server? 回答1: Technically, there should be no problem in doing

问题 I have some sample source code for OpenGL, I wanted to compile a 64bit version (using Delphi XE2) but there's some ASM code which fails to compile, and I know nothing about ASM. Here's the code below, and I put the two error messages on the lines which fail... // Copy a pixel from source to dest and Swap the RGB color values procedure CopySwapPixel(const Source, Destination: Pointer); asm push ebx //[DCC Error]: E2116 Invalid combination of opcode and operands mov bl,[eax+0] mov bh,[eax+1]

问题 In this answer author states: With the 64-bit x86_64 kernel, a 32-bit process can use the entire 4GB address space, except for a couple pages (8KB) at the end of the 4GB address space which are managed by the kernel. What is the purpose of this kernel-managed memory? Shouldn’t it be in the kernel space, to prevent accidental corruption by the user? 回答1: Citing the kernel source: “ Kernel pointers have redundant information, so we can use a scheme where we can return either an error code or a

问题 I have an SVG file that I need to display in a .NET Windows Forms application. This is a common problem. However, the WebBrowser control doesn't work because IE's engine doesn't render my SVG correctly (specifically it ignores the preserve whitespace directive). I looked into Chrome and Firefox controls and they worked great but they are 32-bit only and other references require the project to be compiled in 64-bit mode. Surely there must be some option for displaying correctly rendered SVG in