From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BF9863858C98; Thu, 16 May 2024 12:41:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF9863858C98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1715863295; bh=faDGT70ldT5EcxZ2cJhg79LGxAMcQH5xIDUxBr+KngA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rXup22iJoNXqXJbAZ0VyUteyDgw4gtE2rBPMnjmtcIGhblOjebMMqSFsxsQNJ0naz Yh0x9uEvycd1pBl/vU1k4PS/g9RDL1fxZuf0tCtTDzBiYlwXBcJ58DpIustr1Wjrdm JZF7QHRagx/tWpjd4mq5W9opZwcaEN+wgkqt43Ns= 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, 16 May 2024 12:41:35 +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 #19 from Richard Biener --- (In reply to Robin Dapp from comment #18) [...] > Regarding the mentioned element-wise costing how should we proceed here?= =20 > I'm going to remove the hunk in question, run SPEC2017 on x86 and post a > patch in order to get some data and basis for discussion. Yeah, I think this hunk was put in as a stopgap solution.=