https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84052
--- Comment #5 from PaX Team <pageexec at gmail dot com> --- (In reply to Andrew Pinski from comment #4) > Because debug information happens early on and has many interactions with > the front end. FINISH_TYPE happens early on too and the API promise gcc makes is that it's invoked "After finishing parsing a type" (in practice that's right after c_parser_struct_or_union_specifier for this case). clearly there's a sequencing problem between this and the emission of debug information which means it's either undocumented (gcc bug) or unintended (gcc bug). i don't know which it is but clearly something is not right.
