https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
Tavian Barnes changed:
What|Removed |Added
CC||tavianator at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
Joseph S. Myers changed:
What|Removed |Added
CC||anders.granlund.0 at gmail dot
com
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #9 from joseph at codesourcery dot com ---
On Mon, 29 Oct 2018, egallager at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
>
> --- Comment #8 from Eric Gallager ---
> (In reply to jos...@codesourcery.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #8 from Eric Gallager ---
(In reply to jos...@codesourcery.com from comment #6)
> Rather than piecemeal fixes with no evidence of completeness, I think we
> should disable the smarts around system header macro locations determining
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
Martin Sebor changed:
What|Removed |Added
CC||wellnhofer at aevum dot de
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #6 from joseph at codesourcery dot com ---
Rather than piecemeal fixes with no evidence of completeness, I think we
should disable the smarts around system header macro locations determining
whether diagnostics appear (i.e., the sys
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #5 from Alexander Cherepanov ---
This bug also affects -pedantic-errors, i.e. it's not merely a cosmetic
bug but also a conformance issue. I don't know how -std=c11 can ignore
constraint violations but -pedantic-errors is supposed t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #4 from David Malcolm ---
Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01658.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
--- Comment #2 from joseph at codesourcery dot com ---
Really we need to review warnings and work out in each case what's right
for macros from system headers. If the issue is about the macro's
contents, the warnings should be avoided; if it r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71613
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
11 matches
Mail list logo