From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 25DAA385803F; Thu, 21 Oct 2021 07:30:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 25DAA385803F From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102847] [12 regression] r12-4504 breaks powerpc64 build on power 7 Date: Thu, 21 Oct 2021 07:30:46 +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: 12.0 X-Bugzilla-Keywords: build, ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed cc resolution 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2021 07:30:47 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102847 Kewen Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Last reconfirmed| |2021-10-21 Ever confirmed|0 |1 CC| |rguenth at gcc dot gnu.org Resolution|DUPLICATE |--- --- Comment #4 from Kewen Lin --- (In reply to seurer from comment #3) > I reran my bisects on two different systems and both resolved to=20 >=20 > g:793d2549b173a0a2da6dd20ffc27acb9fd2de73e, r12-4501 >=20 > as when the builds started failing. r12-4500 worked on both systems. Thanks! It makes more sense, I tried my local fix for PR102767 on a Power7 = BE machine yesterday, this issue still existed, seems not an actual dup. Some relevant commits are r11-1945 and r11-6717. In function get_load_store_type, we just simply assign the alignment_support_scheme to dr_unaligned_supported for VMAT_INVARIANT, with= out going through the check in vect_supportable_dr_alignment (including target = hook checks). IIUC, VMAT_INVARIANT memory accesses will end up with scalar accesses, it l= ooks intentional, but it's unexpected for rs6000_builtin_vectorization_cost, as function rs6000_builtin_support_vector_misalignment says it only allows element_size 32 and 64 for misalignment -1. In this failure, it's V16QI (ak= a, element_size 8). Not sure if it's a good idea to change *alignment_support_scheme to dr_alig= ned for VMAT_INVARIANT (also for strided)? Or force *misalignment to zero, the= n we can distinguish this kind of special case in builtin_vectorization_cost hoo= k to avoid ICE?=