https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109125
--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #7 from Gaius Mulley <gaius at gcc dot gnu.org> --- > Created attachment 54675 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54675&action=edit > Proposed fix v3 > > Many thanks for testing and diagnosing the latest bugs. Here is a proposed > fix > for the bool parameters in dtoa and ldtoa: This fixes all but one last failure: +FAIL: gm2/types/run/pass/varient4.mod execution, -O +FAIL: gm2/types/run/pass/varient4.mod execution, -O -g +FAIL: gm2/types/run/pass/varient4.mod execution, -O3 -fomit-frame-pointer +FAIL: gm2/types/run/pass/varient4.mod execution, -O3 -fomit-frame-pointer -fin line-functions +FAIL: gm2/types/run/pass/varient4.mod execution, -Os +FAIL: gm2/types/run/pass/varient4.mod execution, -g gm2.log shows executed /var/gcc/regression/master/11.4-gcc/build/gcc/testsuite/gm2/varient4.x0 with result failFAIL: gm2/types/run/pass/varient4.mod execution, -g There's one unrelated issue here: the "excuted...with result fail" message needs to end in a newline so you can grep for ^FAIL: in the log file. This is from gm2-torture.exp (gm2-torture-execute), where the send_log call needs an "\n"appended. gm2-simple.exp (gm2-simple-execute) has the same issue. The failing test just exits with status 1. Running it under gdb shows that the exit happens after this: 36 zero ; hmm.bar := TRUE ; test(hmm, 3, 1) ; Thread 2 hit Breakpoint 4, d_test (s=0x34bc0 <hmm>, n=3, v=1) at /vol/gcc/src/hg/master/local/gcc/testsuite/gm2/types/run/pass/d.c:44 44 switch (n) { (gdb) p s $1 = (this *) 0x34bc0 <hmm> (gdb) p *$1 $2 = {tag = 0, that = {first = {foo = 0, bar = 16777216, inner = {bt = 0, bf = 0}}, an = 0}, final = 0} (gdb) n 48 case 3: assert(s->that.first.bar == v); break; (gdb) p s->that.first.bar $3 = 16777216 (gdb) p v $4 = 1
