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 EA8513857355; Mon, 15 May 2023 08:40:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EA8513857355
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1684140011;
	bh=az22TSf1J9VbEUgP46rHtjbMuPbDMImd2GjqovmuuSQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Ayj5MVG8GCLrX9r4S5qfExXjr4ajrk401lbEB3P6wf6q5KjDgFzqT68uLNF70AWyT
	 EiJw4c3qhoneflCsZw8baUdDKGtrvs9l7bWUsNKrx036I3Bd3kbmtkRNmO72HnAQ0v
	 nIHpKuoXYMbokqEjziG21zc51Bj1ciP6/i0Sp/h4=
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109610] [14 regression] gcc.target/powerpc/dform-3.c
 fails after r14-172-g0368d169492017
Date: Mon, 15 May 2023 08:40:11 +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: 14.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-109610-4-CqIn25NUwv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109610-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=3D109610

--- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Hongtao.liu from comment #5)
> One solution is add an peephole for handle such redudancy.

Not okay.

> If powerpc maintainer doesn't like this way, another alternative is add a
> target hook in RA to still use GENEREAL_REGS for other targets, but use
> NO_REGS only for x86.

Also not okay.  Please solve the fundamental problem in cost estimation you
created, don't let all targets try to fix it in different ways :-(=