From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 35E493858C78; Thu, 25 Jan 2024 09:34:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 35E493858C78 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706175264; bh=HfB37Noqu0i1wE4M/NMJ4RaTGyF02KUwoI3ECQ5dhKA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=djI3s4YiZpe/DKHqZDvsm4NoGkSAWLysHvusqn3POs6fYYDn7zdU3YZD0hWSHHfMK +N+UixZOflcyoGkCuI4Z8+mY80On+IT3QkL38Hp88iYw36UgoW4XKS7QWfb7X0YUq8 1qS8/X2ic68Pt+VzAhZj+LRVJbPyx39lR5o6QxI0= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113583] Main loop in 519.lbm not vectorized. Date: Thu, 25 Jan 2024 09:34:23 +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: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement 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: 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=3D113583 --- Comment #8 from Richard Biener --- (In reply to JuzheZhong from comment #7) > > But I wonder if we see it is beneficial on some boards, could you teach us > how we can enable vectorization for such case according to uarchs ? If you figure how to optimally vectorize this for a given uarch I can definitely guide you.=