[Bug plugins/65227] Plugin headers are unusable when included after inttypes.h

2015-02-27 Thread Bert.Wesarg at googlemail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65227 --- Comment #4 from Bert Wesarg --- (In reply to Richard Biener from comment #3) > Doumentation bug then. gcc-plugin.h should be the _only_ GCC header to > include. > So inttypes.h is considered a GCC header than? And even if GCC mandates that

[Bug plugins/65227] Plugin headers are unusable when included after inttypes.h

2015-02-27 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65227 Richard Biener changed: What|Removed |Added Keywords||documentation Status|UNCONF

[Bug plugins/65227] Plugin headers are unusable when included after inttypes.h

2015-02-26 Thread Bert.Wesarg at googlemail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65227 --- Comment #2 from Bert Wesarg --- (In reply to Andrew Pinski from comment #1) > You should always include gcc-plugin.h first when compiling plugins. But the documentation in gcc/doc/plugins.texi only reads: The header @file{gcc-plugin.h} must

[Bug plugins/65227] Plugin headers are unusable when included after inttypes.h

2015-02-26 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65227 Andrew Pinski changed: What|Removed |Added Severity|major |normal --- Comment #1 from Andrew Pinski