https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83150
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> --- (In reply to Ben Longbons from comment #3) > (In reply to Andrew Pinski from comment #2) > > Plugins are not well defined in GCC. > > That excuse is getting *really* old. No matter how often you hear it, it is still true. A plugin is not a separate thing running next to GCC. A plugin becomes part of the same compiler process, and it has to play by all the same rules as any other part of the compiler. > So far, the main difficulties I'm hitting are when GCC goes out of its way > to be difficult. It doesn't. It is designed for one purpose; you want to use it some other way. If you have constructive suggestions how to make things easier for plugins (while at the same time not making things harder for everyone else) we'd love to hear them (esp. if accompanied by patches). Your "2." is a real bug I think. "1." not really, that's just a part of the internal GCC design. See above.
