32bit-64bit

I am having some trouble compiling 32-bit GTK+ applications on 64-bit Linux, specifically Ubuntu 10.04. Compiling 64-bit GTK+ applications works fine, and everything is set up to compile 32-bit apps as well, but it doesn't work with GTK+ I have a very simple test program that I am using for trouble shooting that is simply a gtk_init and a gtk_main, which compiles fine as -m64. I am compiling with gcc 4.6.2, calling it with: gcc -m32 gtktest.c `pkg-config --cflags gtk+-2.0` `pkg-config --libs gtk+-2.0` These are the two different kinds of error messages I get: /usr/local/lib/gcc/x86_64-unknown

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? 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 [...] pointer with the same return value. ” The values -1..-4095 (mapping to 0xfffff000–0xffffffff in 32-bit

My program is in 32bit mode running on x86_64 CPU (64bit OS, ubuntu 8.04). Is it possible to switch to 64bit mode (long mode) in user mode temporarily? If so, how? Background story: I'm writing a library linked with 32bit mode program, so it must be 32bit mode at start. However, I'd like to use faster x86_64 intructions for better performance. So I want to switch to 64bit mode do some pure computation (no OS interaction; no need 64bit addressing) and come back to 32bit before returning to caller. I found there are some related but different questions. For example, run 32 bit code in 64 bit

I'm trying to maintain one repository, most everything in my code base is source, but we've got the QuickPDF library which is a bunch of precompiled DCU's. I'd like to put them in version control somehow but I don't want to have yet another option set for win64 that I'm going to forget about before I convert the rest of my trillion LOC codebase to win64. What I was thinking was just having (and quickPDF is just an example, there's nothing special about this library other than its unfortunate precompiledness) ctrls\quickpdf\QuickPDF.pas ctrls\quickpdf\win32[*.dcu] ctrls\quickpdf\win64[*.dcu]

If the OS is 64bit I want to install a 32bit DLL to the Program Files (x86) folder and 64bit DLL to Program Files folder and register them respectively. If it is a 32bit OS I just want to copy the file to the normal program folder and register. How can I do this in Inno Setup? Also will the 64bit DLL be registered by the 64bit regsvr32 program? Here is my code so far. It works fine on 32bit OS but on 64bit OS it dumps both set of files in the Program Files (x86) . [Files] Source: D:\..\32bit files\mylibrary.dll; DestDir: {app}; \ Flags: restartreplace ignoreversion regserver 32bit Source: D:\.

I'm attempting to build a project using MSBuild (v4.0) on a 64-bit machine. For some reason, MSBuild is attempting to load a 32-bit extension, and I cannot figure out why. I've reduced the problem to the smallest set in order to demonstrate the issue. Using the following MSBuild project file: <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0"> <Target Name="test"> <Message Text="bin path: $(MSBuildBinPath)" /> <Message Text="extensions path: $(MSBuildExtensionsPath)" /> <Message Text="extensions path (x86): $(MSBuildExtensionsPath32)" /> <Message Text=

Background: We have acquired a software product that builds to a 32-bit Windows application in Visual Studio. We wish to port this application to 64-bit. A mission-critical component of this code is a black-box static library (.a file) originally built using gFortran by a third party. The original developer has since passed away, and the Fortran source we were able to get was incomplete and not the version this library was built off of (and contains critical bugs not present in the compiled library). They did not use a VCS. Problem: I would like to create a 64-bit static library whose code is