From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 606183858408; Fri, 12 Apr 2024 13:10:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 606183858408 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712927425; bh=jJ8V9u5rHiSYsmiSWrZgJnhJiGOc+rFEe6n6Ooh8Vak=; h=From:To:Subject:Date:In-Reply-To:References:From; b=pbTxaXVyYF1+/ochVlL/nD6ujDJRYim6pbxidtOgkJwjbNgCIfkl7AJTQmMJwFJ67 ery1FkRQDYV4izUVSQpwPZ3J5hVjEI74Br0W5cT2n7N0HOF4BbqIvCu7uFzTaWi9+a ydbyGTTWqR/o2mz2lkicbH0FY9TfmMJH3cDP48J4= From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111231] [12/13/14 regression] armhf: Miscompilation with -O2/-fno-exceptions level (-fno-tree-vectorize is working) Date: Fri, 12 Apr 2024 13:10:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rearnsha at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.4 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=3D111231 --- Comment #29 from Richard Earnshaw --- Sorry, I was looking at the wrong pair of insns. The earlier store to that location was insn 111. 111: [r212:SI (1 MEM[(struct Vec128 *)_179]+0 S4 A64)] =3D {r0:SI..r3:SI} It appears that the problem is a disagreement between alias_set_subset_of () and alias_sets_conflict_p(). The former thinks sets 1 and 2 have a permiss= ible subset relationship (2 is a subset of 1), so removes the later store during postreload. The latter is then used by alias_sets_conflict_p which thinks there is no conflict between the two sets and fails to add a scheduling dependency before sched2.=