<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Jan 6, 2014, at 1:47 PM, Richard Smith <<a href="mailto:richard@metafoo.co.uk">richard@metafoo.co.uk</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">One view on this is simply: -Wsystem-headers means "don't give system headers special treatment when emitting diagnostics”.</span></blockquote><div><br></div><div>This is it exactly. “Treat all headers like normal headers"</div><br><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;"> That would seem to make perfect sense to people developing system headers, and is our current behavior. What is the use case that leads to enabling -Wsystem-headers but not wanting that to lead to errors? PR18327 doesn't make that obvious.</span></blockquote></div><br><div>Not sure I’m following that report, if one doesn’t like that that diagnostic is by default mapped to an error, maybe map it to a warning on the command-line or discuss whether it should not be mapped to error by default ?</div><div>I don’t see a need to complicate what -Wsystem-headers does.</div><div><br></div></body></html>