From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 0CA2B386F452; Mon, 13 May 2024 14:17:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CA2B386F452
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1715609846;
	bh=Y3qgxJzAE1Jfis5Rpy0PI1SDiw8IUVzteBz3gb3+kaM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UlCLnFZDOJkH9B8k6usBkJgvZ05jaiy7UBF8AYNkK4sh9JLX+hJo8Ku2lmFg373EI
	 8ynyup8ba30B8j+b0vwWLyMmXN2F+KKtX2rSSrljtBJo3PQClrn1zQGYsKpLf+64D0
	 oTxKo6TRzYCffRjai+pFOd7GZwZPoX3HK4AsuID8=
From: "rdapp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113583] Main loop in 519.lbm not vectorized.
Date: Mon, 13 May 2024 14:17:24 +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: rdapp 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: <bug-113583-4-gE16ia9KGn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113583-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113583-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113583

--- Comment #18 from Robin Dapp <rdapp at gcc dot gnu.org> ---
A bit of a follow-up:  I'm working on a patch for reassociation that can ha=
ndle
the mentioned cases and some more but it will still require a bit of time to
get everything regression free and correct.  What it does is allow reassoc =
to
look through constant multiplications and negates to provide more freedom in
the optimization process.

Regarding the mentioned element-wise costing how should we proceed here?  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.=