[LLVMbugs] [Bug 7554] New: .o generated by clang is over 2m larger than the one produced by gcc
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Thu Jul 1 15:35:02 PDT 2010
http://llvm.org/bugs/show_bug.cgi?id=7554
Summary: .o generated by clang is over 2m larger than the one
produced by gcc
Product: clang
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: evan at chromium.org
CC: llvmbugs at cs.uiuc.edu
I am looking into why gcc Chrome is ~600mb while clang builds of Chrome are
1.7gb. (Both with debugging symbols.) I've attached the preprocessed version
of one of the files that differs the most between the two compilers.
With the same input file, I can generate two output files:
g++ -pthread -O0 -g -c -o profile.gcc profile.ii
../llvm/Release/bin/clang++ -pthread -O0 -g -c -o profile.gcc profile.ii
Their sizes differ significantly:
-rw-r--r-- 1 evanm evanm 4709032 2010-07-01 15:30 profile.clang
-rw-r--r-- 1 evanm evanm 2570352 2010-07-01 15:30 profile.gcc
gzipped file attached.
llvm$ svn info . tools/clang/ | grep Revision
Revision: 107405
Revision: 107405
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list