public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/5169: [PA-RISC] Bug in optimizer
Date: Wed, 26 Mar 2003 12:26:00 -0000 [thread overview]
Message-ID: <20030326121601.16206.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/5169; it has been noted by GNATS.
From: Alan Modra <amodra@bigpond.net.au>
To: bangerth@dealii.org, Klaus.k.pedersen@nokia.com, Richard.Earnshaw@arm.com,
gcc-bugs@gcc.gnu.org, law@redhat.com, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: target/5169: [PA-RISC] Bug in optimizer
Date: Wed, 26 Mar 2003 22:41:58 +1030
On Tue, Mar 25, 2003 at 02:33:45AM -0000, bangerth@dealii.org wrote:
> Is there any progress on this question?
I haven't looked at this particular problem in over a year, but from
memory I think there may have been some follow-on posts that stated
the underlying problem was inconsistent treatment of paradoxical
subregs on WORD_REGISTER_OPERATIONS machines.
My patch should be regarded as a band-aid rather than a proper
solution.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next reply other threads:[~2003-03-26 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 12:26 Alan Modra [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 14:26 bangerth
2003-03-25 2:35 bangerth
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=20030326121601.16206.qmail@sources.redhat.com \
--to=amodra@bigpond.net.au \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).