search for: 00000ef4

Hi Holger, > Note that I did specify "-g", but not any "-Ox" switches. That > made the size of all *.o files together being 143 MB. LLVM represents debug info as explicit calls to intrinsics. This approach has many advantages, but a possible disadvantage is that it can significantly increase the size of the bitcode. I don't know if that explains your observations.

...that explains your observations. I'm curious > to know how gcc stores debug info... GCC stores debug info in ELF sections of the .o file, e.g.: $ objdump -h wtd.o wtd.o: file format elf32-i386 Sections: Idx Name Size VMA LMA File off Algn 0 .text 00000ef4 00000000 00000000 00000034 2**2 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 1 .data 00000000 00000000 00000000 00000f28 2**2 CONTENTS, ALLOC, LOAD, DATA 2 .bss 00000000 00000000 00000000 00000f28 2**2 ALLOC 3...

I want to share a little LLVM experiment. I tried LLVM on one of my bigger Qt 3.x based projects. I used llvm from SVN trunk (r39999) and SVN llvm-gcc-4.01 (r370) and did compile every file with /usr/src/llvm/dist/bin/g++ -c -pipe -g \ -Wall -Wextra -Wno-sign-compare \ ... lots of -Dxxxx ... \ --emit-llvm -I/usr/share/qt3/mkspecs/default \ -I. -I.. -I../../../include/qt3 -I.obj/ \