https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112486
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #3 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
FWIW you can use "-fmax-error=256" to limit the amount of error messages.
But generally if you want to compile some potentially malicious source code,
you still need to run GCC in a sandbox with an output limit (along with other
resource limits) as GCC security policy explicitly notes.
