From: Jeff Law <law@redhat.com>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
John David Anglin <dave@hiauly1.hia.nrc.ca>
Subject: Re: Emit more REG_EQUIV notes for function args (PR42235)
Date: Mon, 19 Jul 2010 16:51:00 -0000 [thread overview]
Message-ID: <4C44827B.5070305@redhat.com> (raw)
In-Reply-To: <4C4420F2.5010807@codesourcery.com>
On 07/19/10 03:54, Bernd Schmidt wrote:
> On 07/15/2010 07:13 PM, Bernd Schmidt wrote:
>
>> On 07/15/2010 12:28 AM, Jeff Law wrote:
>>
>>> On 07/14/10 15:30, Bernd Schmidt wrote:
>>>
>>>> If necessary I can try to test for a single insn with single_set and
>>>> push it to the sequence otherwise.
>>>>
>>>>
>>> For the mn103, the conversions were single insns...
>>>
>>> Ultimately, I think you have to peek at the insn(s) and see what
>>> registers they set/clobber.
>>>
>> How's this? Bootstrapped and tested on i686-linux. ARM tests in progress.
>>
> This seems to have caused a bootstrap failure on hppa. A QImode value
> is passed in a SImode reg and then should get extended to DImode; we
> must make sure we use a qidi extension. The following patch does that;
> I've not heard back whether it fixes the hppa bootstrap, but it seems to
> work on arm-linux (one extra testsuite failure caused by an unrelated
> change in the same tree). Also bootstrapped on i686-linux. Ok?
>
Assuming John confirms it fixes the PA failure. OK.
jeff
next prev parent reply other threads:[~2010-07-19 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 11:14 Bernd Schmidt
2010-07-14 18:54 ` Jeff Law
2010-07-14 21:30 ` Bernd Schmidt
2010-07-14 22:28 ` Jeff Law
2010-07-15 17:14 ` Bernd Schmidt
2010-07-15 21:26 ` Jeff Law
2010-07-19 9:55 ` Bernd Schmidt
2010-07-19 16:51 ` Jeff Law [this message]
2010-07-19 16:53 ` Bernd Schmidt
2010-07-19 16:59 ` Richard Henderson
2010-07-19 17:09 ` Jeff Law
2010-07-19 19:06 ` John David Anglin
2010-07-21 22:53 ` Bernd Schmidt
2010-07-14 21:48 ` Bernd Schmidt
2010-07-14 22:22 ` Jeff Law
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=4C44827B.5070305@redhat.com \
--to=law@redhat.com \
--cc=bernds@codesourcery.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
/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).