From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E7DAC385840E; Thu, 16 Mar 2023 14:43:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E7DAC385840E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678977785; bh=mQTPF8VKy/pHZTyTh84yPYQxknqdkwXBYg+oBOzxyPg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YKYjDEPDrX0Q1/7ifkzKQ7sBcSqSBvV9DkL+mIY0KO1WGCJwLmkbuq5HMl/6lVder KNdwDrk+as9MvQ7l+uNTSIrRvadYPfrN4byPKxqWW+o3mm5icnjgHb2MFOJDXJwCQT /XEdwERQ9GG2riaEIIJcZAf9xVDfWM14BjH8OXdw= From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/109125] [13 regression] SIGBUS in m2pim_ldtoa_ldtoa Date: Thu, 16 Mar 2023 14:43:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: modula2 X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109125 --- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #7 from Gaius Mulley --- > Created attachment 54675 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54675&action=3Dedit > Proposed fix v3 > > Many thanks for testing and diagnosing the latest bugs. Here is a propos= ed 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=20 +FAIL: gm2/types/run/pass/varient4.mod execution, -O -g=20 +FAIL: gm2/types/run/pass/varient4.mod execution, -O3 -fomit-frame-pointer= =20 +FAIL: gm2/types/run/pass/varient4.mod execution, -O3 -fomit-frame-pointer -fin line-functions=20 +FAIL: gm2/types/run/pass/varient4.mod execution, -Os=20 +FAIL: gm2/types/run/pass/varient4.mod execution, -g=20 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=20 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 :=3D TRUE ; test(hmm, 3, 1) ; Thread 2 hit Breakpoint 4, d_test (s=3D0x34bc0 , n=3D3, v=3D1) at /vol/gcc/src/hg/master/local/gcc/testsuite/gm2/types/run/pass/d.c:44 44 switch (n) { (gdb) p s $1 =3D (this *) 0x34bc0 (gdb) p *$1 $2 =3D {tag =3D 0, that =3D {first =3D {foo =3D 0, bar =3D 16777216, inner = =3D {bt =3D 0,=20 bf =3D 0}}, an =3D 0}, final =3D 0} (gdb) n 48 case 3: assert(s->that.first.bar =3D=3D v); break; (gdb) p s->that.first.bar $3 =3D 16777216 (gdb) p v $4 =3D 1=