From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Sam Tebbs <Sam.Tebbs@arm.com>, Steve Ellcey <sellcey@cavium.com>,
Andreas Schwab <schwab@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"bergner@linux.ibm.com" <bergner@linux.ibm.com>
Subject: Re: [PATCH] combine: Do not combine moves from hard registers
Date: Sat, 10 Nov 2018 16:54:00 -0000 [thread overview]
Message-ID: <acb1f990-067a-2dd5-a3a7-fb1aaa01d5f2@redhat.com> (raw)
In-Reply-To: <20181110045058.GB23873@gate.crashing.org>
On 11/9/18 9:50 PM, Segher Boessenkool wrote:
> On Fri, Nov 09, 2018 at 02:12:22PM -0700, Jeff Law wrote:
>> On 11/8/18 1:34 PM, Segher Boessenkool wrote:
>>> On Thu, Nov 08, 2018 at 03:44:44PM +0000, Sam Tebbs wrote:
>>>> Does your patch fix the incorrect generation of "scvtf s1, s1"? I was
>>>> looking at the issue as well and don't want to do any overlapping work.
>>>
>>> I don't know. Well, there are no incorrect code issues I know of at all
>>> now; but you mean that it is taking an instruction more than you would
>>> like to see, I suppose?
>> Which is ultimately similar to the 3 regressions HJ has reported on x86_64.
>
> I just wish those bug reports would mature from "oh hey this patch changed
> some stuff" to "oh yeah this made some existing problems (in the backend,
> or common code, hey let's blame RA because it's most obvious here, why not!)
> more obvious".
>
> All those PRs show situations where we could generate better code. None
> of those PRs show situations where the combine patches were at fault.
>
> Blaming others is not going to improve your code one bit.
>
>
> (And yes, i'll commit one further improvement patch _right now_).
I agree to a degree, but it's also the case that these are clearly code
quality regressions triggered by your changes. Your help in resolving
them would be greatly appreciated.
Jeff
next prev parent reply other threads:[~2018-11-10 16:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 21:06 Segher Boessenkool
2018-10-22 22:07 ` Jeff Law
2018-10-22 22:46 ` Segher Boessenkool
2018-10-23 10:54 ` Christophe Lyon
2018-10-23 12:36 ` Christophe Lyon
2018-10-23 13:10 ` Segher Boessenkool
2018-10-23 13:30 ` Christophe Lyon
2018-10-23 13:08 ` Segher Boessenkool
2018-10-23 13:50 ` Christophe Lyon
2018-10-24 1:50 ` Segher Boessenkool
2018-10-24 9:52 ` Christophe Lyon
2018-11-02 22:19 ` Renlin Li
2018-11-02 23:03 ` Segher Boessenkool
2018-11-02 23:54 ` Segher Boessenkool
2018-11-03 2:34 ` Jeff Law
2018-11-05 12:35 ` Renlin Li
2018-11-05 18:16 ` Renlin Li
2018-11-07 23:02 ` Segher Boessenkool
2018-11-09 10:21 ` Richard Earnshaw (lists)
2018-11-05 22:50 ` Segher Boessenkool
2018-10-24 9:38 ` Paul Hua
2018-10-23 16:16 ` Andreas Schwab
2018-10-23 16:28 ` Segher Boessenkool
2018-10-24 12:24 ` Andreas Schwab
2018-10-26 17:41 ` Steve Ellcey
2018-10-26 18:37 ` Segher Boessenkool
[not found] ` <7bc8697f-a09e-627f-b032-eba5ecb682ac@arm.com>
2018-11-08 20:34 ` Segher Boessenkool
2018-11-09 21:12 ` Jeff Law
2018-11-10 4:51 ` Segher Boessenkool
2018-11-10 16:54 ` Jeff Law [this message]
2018-11-12 11:57 ` Sam Tebbs
[not found] ` <e9104024-2f6a-6cb8-e366-39b96f7a72f2@arm.com>
2018-11-12 12:54 ` Segher Boessenkool
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acb1f990-067a-2dd5-a3a7-fb1aaa01d5f2@redhat.com \
--to=law@redhat.com \
--cc=Sam.Tebbs@arm.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
--cc=segher@kernel.crashing.org \
--cc=sellcey@cavium.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).