[LLVMbugs] [Bug 8129] New: clang++ not suppressing warnings in standard headers.
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Fri Sep 10 22:54:07 PDT 2010
http://llvm.org/bugs/show_bug.cgi?id=8129
Summary: clang++ not suppressing warnings in standard headers.
Product: clang
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: lhames at gmail.com
CC: llvmbugs at cs.uiuc.edu, dgregor at apple.com
Created an attachment (id=5478)
--> (http://llvm.org/bugs/attachment.cgi?id=5478)
Test case.
Running
clang++ -Wall -Werror -c test.cpp
on the attached test case (an empty c++ file which #includes valarray)
terminates with warnings treated as errors (attached below). I think this
should be suppressed for standard headers, right?
System is Ubuntu Linux 10.04 (AMD64).
- Lang.
clang++ output:
error: class '_Array' was previously declared as a struct [-Wmismatched-tags]
In file included from foo.cpp:1:
In file included from /usr/include/c++/4.4/valarray:561:
/usr/include/c++/4.4/bits/valarray_after.h:57:24: note: in instantiation of
template class 'std::valarray<unsigned long>' requested here
{ return _M_index.size(); }
^
In file included from foo.cpp:1:
In file included from /usr/include/c++/4.4/valarray:86:
/usr/include/c++/4.4/bits/valarray_array.h:409:12: note: previous use is here
struct _Array
^
error: class '_Array' was previously declared as a struct [-Wmismatched-tags]
In file included from foo.cpp:1:
In file included from /usr/include/c++/4.4/valarray:565:
/usr/include/c++/4.4/bits/mask_array.h:143:27: note: in instantiation of
template class 'std::valarray<bool>' requested here
: _M_sz(__s), _M_mask(__m), _M_array(__a) {}
^
In file included from foo.cpp:1:
In file included from /usr/include/c++/4.4/valarray:86:
/usr/include/c++/4.4/bits/valarray_array.h:409:12: note: previous use is here
struct _Array
^
2 errors generated.
--
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