https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118401
Bert Wesarg changed:
What|Removed |Added
CC||Bert.Wesarg at googlemail dot
com
Assignee: unassigned at gcc dot gnu.org
Reporter: Bert.Wesarg at googlemail dot com
Target Milestone: ---
Created attachment 58251
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58251&action=edit
Reduced and prepocesed target_struct_map.4.c
target_struct_map.4.c f
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
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
Priority: P3
Component: plugins
Assignee: unassigned at gcc dot gnu.org
Reporter: Bert.Wesarg at googlemail dot com
GCC 5 20150215 Snapshot.
When the gcc-plugin.h header is included after the inttypes.h header, than the
compilation breaks. Used compiler:
$ g++ -v
Using
: critical
Priority: P3
Component: plugins
Assignee: unassigned at gcc dot gnu.org
Reporter: Bert.Wesarg at googlemail dot com
Created attachment 34885
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34885&action=edit
file which includes gcc-plugin.
