Compiling 32-bit programme on 64-bit GCC in C & C++

Compilers (64-Bit) for Microsoft Windows

The following companies provide 64-bit compilers for Microsoft Windows.

• Intel: It provides C/C++ and Fortran compilers for EM64T and compatible systems running the Microsoft Windows operating system.
• Microsoft: It provides C/C++ compilers for AMD64 architecture-based systems running the Microsoft Windows operating system. The current version is Visual Studio 2008.
• PGI: The Portland Group (PGI) Toolkits are composed of high-performance C, C++ and/or Fortran Compiler(s), a debugger and a performance profiler for 32-bit and 64-bit AMD64 and EM64T processor-based Windows platforms. The latest PGI Edition 7 provides leading-edge application performance on AMD64 next-generation systems and supports features like auto-parallelisation, OS native multithreading, OpenMP multithreading models, and MPI programming for AMD64 architecture-based multicore shared-memory and distributed-memory cluster-based systems.

Also read - AMD vs Intel

Compilers (32-Bit) for Linux: 

The following companies provide 32-bit compilers for x86 Linux. These compilers also run on 64-bit Linux Operating systems, running on AMD Athlon 64 processor-based platforms, AMD Opteron™ processor-based platforms, or AMD Family 10h processor-based platforms.

• GCC: The GCC provides C, C++ and Fortran compilers for x86 Linux and Sun Solaris. This application note, however, does not discuss the GCC compilers for Sun Solaris; it discusses only GCC compilers for Linux. Different Linux distributions offer different versions of the GCC compiler. This application note focuses on the recommended compilers for the following major Linux distributions for workstations and servers—SuSE Linux Enterprise Server 8, SuSE Linux Enterprise Server 9, SuSE Linux Enterprise Server 10, SuSE Linux 10.1, SuSE Linux 10.2, Red Hat Enterprise Linux 3 and Red Hat Enterprise Linux 4. This application note also briefly discusses the GCC 4.2 compiler, which is the current GCC version from the Free Software Foundation (FSF).
• Intel: It provides C, C++ and Fortran compilers for x86 Linux. This document also talks about two previous versions of the compiler, 9.1 and 8.1, because they are comparable in performance to the current version (when running on AMD platforms) and are still in use.
• PathScale: It provides C, C++ and Fortran compilers for x86 Linux.

Compilers (32-Bit) for Microsoft Windows: 

The following companies provide 32-bit compilers for Microsoft Windows.

• Intel: It provides C, C++ and Fortran compilers for x86 Microsoft Windows. This document also talks about two previous versions of the compiler, 9.1 and 8.1, because they are comparable in performance to the current version and are still in use.
• Microsoft: It provides C/C++ compilers for x86 Microsoft Windows.
• PGI: The Portland Group (PGI) Toolkits are composed of high-performance C, C++ and/or Fortran Compiler(s), a debugger, and a performance profiler for 32-bit and 64-bit AMD64 and EM64T processor-based Windows platforms. The latest PGI Edition 7 provides leading-edge application performance on AMD64 next-generation systems and supports features like auto-parallelization, OS native multithreading, OpenMP multithreading models, and MPI programming for AMD64 architecture-based multicore shared-memory and distributed-memory cluster-based systems.

How to check whether a program is compiled with 32-bit after adding a “-m32” flag?

We can easily check this by the following programme.

filter_none
edit
play_arrow

brightness_5
// C program to demonstrate difference
// in output in 32-bit and 64-bit gcc
// File name: geek.c

#include<stdio.h>

int main()
{
printf(“Size = %lu”, sizeof(size_t));
}

Compile the above program in Linux by these two different commands, Default 64-bit compilation.

Input: gcc -m64 geek.c -o out
Output: ./out
Size = 8
Forced 32-bit compilation,

Input: gcc -m32 geek.c -o out
Output: ./out
Size = 4

Also See, cpp abstract class

Some Other Methods Are:

This really depends on the application and how it has been coded. Some code can just be recompiled with a 64-bit compiler and it will just work, but usually, this only happens if the code has been designed with portability in mind.

If the code has a lot of assumptions about the size of native types and pointers, if it has a lot of bit packing hacks or of it talks to an external process using a byte specified protocol but using some assumptions about the size of native types then it may require some, or a lot, of work to get a clean compile.

Pretty much every cast and compiler warning is a red flag that needs checking out. If the code wasn’t “warning clean” to start with then that is also a sign that a lot of work may be required.

Well, fundamentally, the number of changes are fairly small, but it’ll still be a major task if the application isn’t carefully written to be somewhat portable to begin with.

The main difference is that pointers are 64 bit wide, but most other data types are unchanged. An int is still 32 bit and a long is probably also still 32 bit. So if your code casts between ints and pointers, that’s going to break. Similarly, any struct or similar which depends on a specific offset to a member may break because other members may now be bigger, and so change the offset.