From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9C9BC385840B; Mon, 7 Aug 2023 13:30:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9C9BC385840B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1691415034; bh=qWXzElK3day8ULQY/XFnDC2wh86k5meaEHFcCgfbSOs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NCY5EaXnxQjwSCtazScTzH2Ny38Dm7QCFFDLoVwdTbKHuRU8uyXaP3KUI+FSBJm3s Pf8iFy126cJ+xd0gUW3KiKgWnndhfK4adkjzyCNMluwGu930W9D6kryD3oNbQ3ed/W rWl9tY7kri61SrwQVPH0f/x22QtOh8A5C4mcp90A= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110935] Missed BB reduction vectorization because of missed eliding of a permute Date: Mon, 07 Aug 2023 13:30:34 +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: 13.1.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget cf_known_to_fail cc keywords 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=3D110935 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-*-* Known to fail| |13.2.1, 14.0 CC| |rsandifo at gcc dot gnu.org Keywords| |missed-optimization --- Comment #1 from Richard Biener --- I didn't find where we make sure to elide the "outgoing" permute of a reduction, but I think we only have testcases for the loop vectorization ca= se.=20 Can you suggest where we'd do this? Note we do not represent the plus reduction operation but the whole SLP instance has just a single node (with load permutation)=