From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AA68D3858CD1; Wed, 22 May 2024 11:59:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AA68D3858CD1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1716379194; bh=v4fRN5UkR5dyGI7MWpe+CMYrpgHS7deYa25EfIWeUj0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M2CM8O8aH6i1O4JNRimntlI+RRetG0q3kwFs9gIanQx7+Fr57RBI9noHZboudx/m+ iTyM8jM7lC9OqrqlvSb9ESXY0HXJqFYx/kNnrn523TdcSSHCxqDivm2G6DwAfr61PW nT+6zR3Q1MQCFjsnYMRweyV14lU4mT95UsRu0T2o= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/115138] [15 Regression] Bootstrap compare-debug fail after r15-580-gf3e5f4c58591f5 Date: Wed, 22 May 2024 11:59:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 15.0 X-Bugzilla-Keywords: build, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 15.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=3D115138 --- Comment #15 from Richard Biener --- Indeed with boostrap-O3 I can see Comparing stages 2 and 3 Bootstrap comparison failure! gcc/d/opover.o differs since both have debug info with bootstrap-O3 the difference is only - 18: 0000000000000b0c 4 OBJECT LOCAL DEFAULT 6 CSWTCH.154 + 18: 0000000000000b0c 4 OBJECT LOCAL DEFAULT 6 CSWTCH.155 there's already differenes in SRA and even local-fnsummary. In fact gimplification shows --- ../prev-gcc/d/opover.d.006t.gimple 2024-05-22 13:50:13.437438763 +0200 +++ d/opover.d.006t.gimple 2024-05-22 13:51:08.710863322 +0200 @@ -5158,57 +5158,58 @@ overflow =3D 0; newLength.100_2 =3D newLength; newLength.101_3 =3D newLength.100_2; + newLength.102_4 =3D newLength.101_3; D.12117 =3D .ADD_OVERFLOW (typeInfoSize, 1); as first difference (but the .original dumps are the same). That's in the __setArrayAllocLength function. Note the opover.d compile doesn't even use -O3, so this is all extremely odd. It would somehow point at a miscompile of the stage2 compiler by the stage1 compiler manifesting itself only in this change ... So the logical next step would be to bisect stage1/stage2 object files of d21 and see which stage2 object is miscompiled.=