[Bug c/63326] pragma GCC causes wrong code generation

2014-09-24 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326

Manuel López-Ibáñez  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
   Last reconfirmed||2014-09-24
 CC||manu at gcc dot gnu.org
 Resolution|INVALID |---
 Ever confirmed|0   |1

--- Comment #3 from Manuel López-Ibáñez  ---
If you use #pragma GCC system_header, you get a different result, so this seems
a bug to me (whatever the behavior, it should not depend on the type of
#pragma). At the very least, GCC could give a warning if the #pragma is the
only statement in a if/else/while/do/for body, since this is probably a bug.

[Bug c/63326] pragma GCC causes wrong code generation

2014-09-24 Thread dietmar.schind...@manroland-web.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326

--- Comment #2 from Dietmar Schindler  ---
(In reply to Andrew Pinski from comment #1)
> #pragma are considered statements.

This can't be entirely true, since #pragma can be used where statements cannot
(outside of functions), and #pragma STDC certainly isn't considered a
statement.
At least, this implementation-defined behaviour has to be documented (hasn't
it?), and I couldn't find mention of it in the documentation. Would you
recommend filing a separate documentation bug report?


[Bug c/63326] pragma GCC causes wrong code generation

2014-09-21 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63326

Andrew Pinski  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Andrew Pinski  ---
#pragma are considered statements.