https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84052
--- Comment #3 from PaX Team <pageexec at gmail dot com> --- (In reply to Andrew Pinski from comment #1) > Plugins issues like this should reported to the plugin author and not to gcc. what makes you think it's a plugin issue? i reported several gcc bugs myself over the years that i ran across while developing plugins (some have yet to be addressed fwiw). this case is no different, it's a gcc bug where sometimes gcc emits debug info for a type that has not even been constructed yet.
