I’ve found the simplest way to do this is to import the two methods with different names, and calling the right one. The DLL won’t be loaded until the call is made so it’s fine: [DllImport(“MyDll32.dll”, EntryPoint = “Func1”, CallingConvention = CallingConvention.Cdecl)] private static extern int Func1_32(int var1, int var2); [DllImport(“MyDll64.dll”, EntryPoint = “Func1”, CallingConvention … Read more
On a 32-bit machine: Any CPU: runs as a 32-bit process, can load Any CPU and x86 assemblies, will get BadImageFormatException if it tries to load an x64 assembly. x86: same as Any CPU. x64: BadImageFormatException always. On a 64-bit machine: Any CPU: runs as a 64-bit process, can load Any CPU and x64 assemblies, … Read more
x86 is the name of the architecture that it’s built to run on (the name comes from a series of old Intel processors, the names of which all ended in 86, The first of which was the 8086). Although x86 was originally a 16-bit architecture, the version in use today is the 32-bit extension. x64 … Read more
I can reproduce this on 4.5.2. No RyuJIT here. Both x86 and x64 disassemblies look reasonable. Range checks and so on are the same. The same basic structure. No loop unrolling. x86 uses a different set of float instructions. The performance of these instructions seems to be comparable with the x64 instructions except for the … Read more
Yes, it is absolutely no problem. You could even have multiple versions of both 32bit and 64bit Java installed at the same time on the same machine. In fact, i have such a setup myself.
objdump seems like the best way: objdump -f libfoo.a | grep ^architecture
My JVM does this pretty straightforward thing to the inner loop when you use longs: 0x00007fdd859dbb80: test %eax,0x5f7847a(%rip) /* fun JVM hack */ 0x00007fdd859dbb86: dec %r11 /* i– */ 0x00007fdd859dbb89: mov %r11,0x258(%r10) /* store i to memory */ 0x00007fdd859dbb90: test %r11,%r11 /* unnecessary test */ 0x00007fdd859dbb93: jge 0x00007fdd859dbb80 /* go back to the loop top … Read more
One of the more interesting ways I’ve seen is this: if (IntPtr.Size == 4) { // 32-bit } else if (IntPtr.Size == 8) { // 64-bit } else { // The future is now! } To find out if OTHER processes are running in the 64-bit emulator (WOW64), use this code: namespace Is64Bit { using … Read more
Here is what I’ve done in a previous project, which will require the manual edition of the .csproj file(s). You also need separate directories for the different binaries, ideally siblings of each other, and with the same name as the platform you are targeting. After adding a single platform’s references to the project, open the … Read more
Updated answer: You can make use of the z and t modifiers to handle NSInteger and NSUInteger without warnings, on all architectures. You want to use %zd for signed, %tu for unsigned, and %tx for hex. This information comes courtesy of Greg Parker. Original answer: The official recommended approach is to use %ld as your … Read more