Closed
Bug 773768
Opened 12 years ago
Closed 12 years ago
STL: Add another stl file to the "FIXME" list
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
FIXED
mozilla17
People
(Reporter: espindola, Unassigned)
References
Details
Attachments
(1 file)
Code we got from chromium uses <tuple>, so we should add it to stl-headers. I found this because clang is stricter than gcc on redeclarations without visibilities and we were getting a preprocessed file that looked like #pragma GCC visibility push(hidden) .... #pragma GCC visibility push(default) contents of a libstdc++ header that forward declares tuple_element. #pragma GCC visibility pop ... contents of libstdc++'s tuple, which defines tuple_element .... When we see the forward declaration we think that tuple_element has default visibility, but then when we find out the definition we see it has hidden visibility. This can also cause problems if only the tuple header is included and we conclude that the types declared in there are hidden.
Reporter | ||
Updated•12 years ago
|
Attachment #641999 -
Flags: review?(benjamin)
Reporter | ||
Updated•12 years ago
|
Blocks: clang-macosx
Updated•12 years ago
|
Attachment #641999 -
Flags: review?(benjamin) → review?(jones.chris.g)
Comment on attachment 641999 [details]
add tuple to stl-headers
This isn't an exception-safety review, this is extending the list of headers we use but haven't reviewed. Please update this bug accordingly.
r=me for extending that list.
Attachment #641999 -
Flags: review?(jones.chris.g) → review+
Reporter | ||
Updated•12 years ago
|
Summary: STL: Review exception safety of <tuple> for gcc and MSVC → STL: Add another stl file to the "FIXME" list
Comment 2•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1cbe2e404e80
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in
before you can comment on or make changes to this bug.
Description
•