From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: bernds@codesourcery.com (Bernd Schmidt)
Cc: law@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: Emit more REG_EQUIV notes for function args (PR42235)
Date: Mon, 19 Jul 2010 19:06:00 -0000 [thread overview]
Message-ID: <20100719190613.DCFD54D39@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <4C4482CD.60900@codesourcery.com> from "Bernd Schmidt" at Jul 19, 2010 06:52:29 pm
> On 07/19/2010 06:51 PM, Jeff Law wrote:
> > Assuming John confirms it fixes the PA failure. OK.
>
> Yeah, it didn't, and I think I missed a gen_lowpart in there anyway :-(
> Now trying to do something with the compilefarm PA machine, although
> I'm not sure it's a 64-bit one (is it?)
I never use it. HP-UX on "current" machines supports both 32 and 64-bit.
However, generating the initial 64-bit gcc version is still a bit tricky
if it is not present. Linux only has a 32-bit runtime.
The failure was a null pointer fault. However, it has been passed through
multiple layers of inlined functions, and gdb isn't working well. So,
I haven't been able to find the fault. I think I'll retry the testsuite
to see if I can find some more simple failures.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2010-07-19 19:06 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
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 [this message]
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=20100719190613.DCFD54D39@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@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).