https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115386
--- Comment #4 from Sam James <sjames at gcc dot gnu.org> --- meh: ==2441836== Warning: set address range perms: large range [0x59d5f040, 0x78483b50) (undefined) ==2441836== Warning: set address range perms: large range [0x59d5f028, 0x78483b68) (noaccess) ==2441836== Stack overflow in thread #1: can't grow stack to 0x1ffe001000 ==2441836== Stack overflow in thread #1: can't grow stack to 0x1ffe001000 ==2441836== Can't extend stack to 0x1ffe0010b8 during signal delivery for thread 1: ==2441836== no stack segment ==2441836== ==2441836== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==2441836== Access not within mapped region at address 0x1FFE0010B8 ==2441836== Stack overflow in thread #1: can't grow stack to 0x1ffe001000 ==2441836== at 0x117FBE8: gt_ggc_mx_rtx_def(void*) (gtype-desc.cc:326) ==2441836== If you believe this happened as a result of a stack ==2441836== overflow in your program's main thread (unlikely but ==2441836== possible), you can try to increase the size of the ==2441836== main thread stack using the --main-stacksize= flag. ==2441836== The main thread stack size used in this run was 16777216.
