From: Jeff Law <law@redhat.com>
To: Peter Bergner <bergner@linux.ibm.com>,
Vladimir N Makarov <vmakarov@redhat.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC][PATCH LRA] WIP patch to fix one part of PR87507
Date: Mon, 22 Oct 2018 22:08:00 -0000 [thread overview]
Message-ID: <5391dd89-e511-76e8-a22a-0d3692b44d19@redhat.com> (raw)
In-Reply-To: <ca2d2a92-e8bc-4237-15cb-a3d06617b53b@linux.ibm.com>
On 10/19/18 4:39 PM, Peter Bergner wrote:
> On 10/19/18 4:16 PM, Peter Bergner wrote:
>> Thoughts? I'll note that this does not fix the S390 bugs, since those seem
>> to be due to problems with early clobber operands and "matching" constraint
>> operands. I'm still working on that and hope to have something soon.
> [snip]
>> * lra-constraints.c (process_alt_operands): Abort on illegal hard
>> register usage. Prefer reloading non hard register operands.
>
> I stand corrected. Using this patch, plus Segher's combine patch, I am
> able to bootstrap s390x-linux. I'm running the test suite to see whether
> that looks clean as well. Maybe those s390 issues were related to combine
> pushing hard regs into patterns and we just weren't handling them well?
>
> Jeff, maybe once Segher commits his patch, can you give this patch a try
> on your testers?
Once committed to the trunk it's automatically picked up :-) In fact,
commits to the trunk are triggers, though in reality there's *always*
something changing from one day to the next in the various relevant
repos (gcc, binutils, linux kernel, glibc & newlib).
It's only testing patches that aren't on the trunk that require manual
intervention.
jeff
next prev parent reply other threads:[~2018-10-22 20:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 21:51 Peter Bergner
2018-10-20 6:47 ` Peter Bergner
2018-10-20 21:05 ` Segher Boessenkool
2018-10-22 22:08 ` Jeff Law [this message]
2018-10-23 0:25 ` Peter Bergner
2018-10-23 1:16 ` Peter Bergner
2018-10-27 23:25 ` Peter Bergner
2018-11-06 20:28 ` Jeff Law
2018-11-07 0:14 ` Segher Boessenkool
2018-11-07 16:29 ` Peter Bergner
2018-11-07 17:36 ` Jeff Law
2018-11-07 17:45 ` Peter Bergner
2018-11-08 2:17 ` Peter Bergner
2018-11-08 22:07 ` Jeff Law
2018-11-08 22:42 ` Peter Bergner
2018-10-23 4:54 ` Segher Boessenkool
2018-10-23 6:47 ` Peter Bergner
2018-10-25 0:55 ` Jeff Law
2018-10-20 17:23 ` Segher Boessenkool
2018-10-22 23:23 ` Vladimir Makarov
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=5391dd89-e511-76e8-a22a-0d3692b44d19@redhat.com \
--to=law@redhat.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=vmakarov@redhat.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).