Closed
Bug 549766
Opened 15 years ago
Closed 1 year ago
IPDL: Suppress MSVC warning 4530 in generated C++
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cjones, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [build_warning])
We get a bunch of warnings like
C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE\ostream(520) : warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc
Elem,_Traits>::put(_Elem)'
with
[
_Elem=wchar_t,
_Traits=std::char_traits<wchar_t>
]
C:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE\ostream(603) : see reference to class template instantiation 'std::basic_ostream<_Elem,_Traits>' being compiled
with
[
_Elem=wchar_t,
_Traits=std::char_traits<wchar_t>
]
because mozilla code is built with -fno-exceptions, but includes chromium code that includes STL code that uses try/catch, apparently.
Reporter | ||
Comment 1•15 years ago
|
||
See http://pastebin.org/100068 for more.
Updated•14 years ago
|
Blocks: buildwarning
Whiteboard: [build_warning]
![]() |
||
Comment 2•12 years ago
|
||
Fixed by config/msvc-stl-wrapper.template.h from Bug 551254...?
(Not very sure though, sorry)
Flags: needinfo?
![]() |
||
Comment 3•12 years ago
|
||
cjones: You fixed Bug 551254, so it seems like you would be in the best position to answer the question in Comment 2.
Thanks ahead of time...
Flags: needinfo? → needinfo?(cjones.bugs)
Reporter | ||
Comment 4•12 years ago
|
||
No, I don't think that patch would have made this warning go away. But, are we sure that this warning is still generated? I'm not sure that any gecko code still uses std::ostream.
Flags: needinfo?(cjones.bugs)
![]() |
||
Comment 5•12 years ago
|
||
(In reply to Chris Jones [:cjones] mostly inactive; ni?/f?/r? if you need me from comment #4)
> No, I don't think that patch would have made this warning go away.
Ah. Thanks!
Updated•3 years ago
|
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•