On 3/30/2026 6:16 AM, Filip Kastl wrote:
Hi.
This is the second version of this patch. In this version:
- I've also modified gcc.cc instead of just toplev.cc (so both places in GCC's
codebase where 'stack_limit_increase ()' gets called are now patched
- I correctly request more memory when GCC *is* built with ASAN. I switched
that around in v1.
Please also consider this to be a ping.
Btw, if this isn't a stage 4 material, do tell me and I'll postpone pinging to
stage 1 :).
Cheers,
Filip Kastl
-- 8< --
64MB stack is not enough for running
gcc/testsuite/gcc.c-torture/compile/limits-exprparen.c with an
ASAN-instrumented GCC. Ask for more stack if GCC was compiled with ASAN
instrumentation.
PR sanitizer/124206
gcc/ChangeLog:
* gcc.cc (driver::global_initializations): Ask for 128MB stack
instead of just 64MB when __SANITIZE_ADDRESS__ is defined.
* toplev.cc (toplev::main): Ditto.
I'm not excited by new #ifdefs. I don't guess we have any runtime way
to check for asan being enabled? Assuming the answer to that is no, we
don't have a way to check that, then this is OK for gcc-17.
jeff
