https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114222
Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at gcc dot gnu.org --- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> --- More likely the test is running out of address space. The default linker script has a pretty small address space and the text will commonly clash with the heap/stack. Naturally that corrupts the text segment causing all kinds of interesting problems -- worse yet, the problems are intermittent as they depend on precisely what gets clobbered within the text segment and what value ends up in the text segment. The easiest way to check for that is throw the test into the debugger and run it. Assuming it faults, disassemble the instruction at the fault point. Then use objdump to disassemble the binary and see if the instruction has been changed.