https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115386
--- Comment #7 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Richard Biener from comment #6)
> Are you using a compiler with release checking?
No, with asan & ubsan.
I tried running cc1 under gdb and got this backtrace:
#0 0x0000000000b54615 in gt_ggc_mx_rtx_def (x_p=0x7fffe939bd00)
at gtype-desc.cc:323
#1 0x0000000000b54829 in gt_ggc_mx_rtx_def (x_p=<optimized out>)
at gtype-desc.cc:940
#2 0x0000000000b55405 in gt_ggc_mx_rtx_def (x_p=<optimized out>)
at gtype-desc.cc:717
#3 0x0000000000b55405 in gt_ggc_mx_rtx_def (x_p=<optimized out>)
at gtype-desc.cc:717
#4 0x0000000000b55405 in gt_ggc_mx_rtx_def (x_p=<optimized out>)
at gtype-desc.cc:717
#5 0x0000000000b55405 in gt_ggc_mx_rtx_def (x_p=<optimized out>)
at gtype-desc.cc:717
That continues on for a depth of more than 1000 frames.
Interestingly, the code compiles fine with a gcc built with valgrind.
foundBugs $ ~/gcc/results.20240608.valgrind/bin/gcc -w -g -O3 bug1034.c
foundBugs
