[LLVMbugs] [Bug 21299] New: Debugging info being generated for unused typedefs
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Thu Oct 16 10:34:01 PDT 2014
http://llvm.org/bugs/show_bug.cgi?id=21299
Bug ID: 21299
Summary: Debugging info being generated for unused typedefs
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangbugs at nondot.org
Reporter: sunil_srivastava at playstation.sony.com
CC: dgregor at apple.com, llvmbugs at cs.uiuc.edu
Classification: Unclassified
Following small example generates debug info for _Longlong. It should not.
Added over hundreds of such cases from system include files, this can add
significant bulk to the debug info.
This is a 3.4 to 3.5 regression. Current TOT also generates it.
typedef long long _Longlong;
namespace std { using ::_Longlong; }
void foo() {}
+ clang35/bin/clang++ -g -S -O2 -I. -o x-35.s x.cpp
+ clang34/bin/clang++ -g -S -O2 -I. -o x-34.s x.cpp
+ wc x-34.s x-35.s
166 547 6194 x-34.s
231 830 9456 x-35.s
397 1377 15650 total
+ grep _Long x-34.s x-35.s
x-35.s: .asciz "_Longlong"
x-35.s: .asciz "_Longlong" # External Name
Interestingly, gcc4.8 also generates _Longlong, but I consider that a gcc bug.
Clang 3.4 did not generate _Longlong; that was correct.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141016/2f05d0fd/attachment.html>
More information about the llvm-bugs
mailing list