C does not do name mangling, though it does pre-pend an underscore to function names, so the printf(3) is actually _printf in the libc object. In C++ the story is different. The history of it is that originally Stroustrup created “C with classes” or cfront, a compiler that would translate early C++ to C. Then … Read more
I found the following working solution. First create file memcpy.c: #include <string.h> /* some systems do not have newest memcpy@@GLIBC_2.14 – stay with old good one */ asm (“.symver memcpy, memcpy@GLIBC_2.2.5”); void *__wrap_memcpy(void *dest, const void *src, size_t n) { return memcpy(dest, src, n); } No additional CFLAGS needed to compile this file. Then link … Read more
Most Windows process (*.exe) are loaded in (user mode) memory address 0x00400000, that’s what we call the “virtual address” (VA) – because they are visible only to each process, and will be converted to different physical addresses by the OS (visible by the kernel / driver layer). For example, a possible physical memory address (visible … Read more
At the moment it is compiling bigger projects on Ubuntu 10.04. Here you can install and integrate it easily with the binutils-gold package (if you remove that package, you get your old ld). Gcc will automatically use gold then. Some experiences: gold doesn’t search in /usr/local/lib gold doesn’t assume libs like pthread or rt, had … Read more
To link C++ code, you need to use the g++ command, not the gcc command. When compiling, the gcc command knows that it’s compiling C++ code because of the .cpp suffix (but it’s a good idea to use the g++ command anyway). When linking, the gcc command just sees a bunch of .o files. The … Read more
IIRC, In GCC you can provide the –stack,[bytes] parameter to ld. E.g. gcc -Wl,–stack,16777216 -o file.exe file.c To have a stack of 16MiB, I think that the default size is 8MiB.
You could try (ld(2)): –whole-archive For each archive mentioned on the command line after the –whole-archive option, include every object file in the archive in the link, rather than searching the archive for the required object files. This is normally used to turn an archive file into a shared library, forcing every object to be … Read more
Templated code implementation should never be in a .cpp file: your compiler has to see them at the same time as it sees the code that calls them (unless you use explicit instantiation to generate the templated object code, but even then .cpp is the wrong file type to use). What you need to do … Read more
Looking at this thread you can see that it can be done. The guys at GNU suggest gcc foo.c -Wl,-Bstatic -lbar -lbaz -lqux -Wl,-Bdynamic -lcorge -o foo.exe
Neither GCC nor Clang is a linker, and ICF needs to be done by the linker, or at least with cooperation with the linker. Edit: They don’t do ICF, so yes, distinct instantiations produce distinct code. The GNU gold linker supports ICF with the –icf option, which needs the GCC option -ffunction-sections to be used. … Read more