https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117917
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
Status|UNCONFIRMED |RESOLVED
Keywords| |diagnostic
Resolution|--- |INVALID
--- Comment #2 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Yes it finishes. If redirecting the message to /dev/null it spends 20 seconds
for me.
Not a bug. This is one of the reasons we say
The compiler driver processes source code, invokes other programs
such as the assembler and linker and generates the output result,
which may be assembly code or machine code. Compiling untrusted
sources can result in arbitrary code execution and unconstrained
resource consumption in the compiler. As a result, compilation of
such code should be done inside a sandboxed environment to ensure
that it does not compromise the host environment.
in SECURITY.md.
Use -fmax-errors= and/or just pipe the stderr to an external program to
truncate it if you want to limit the output amount. But even with the limit
you still need a sandbox if compiling some untrusted source code.
