From: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bug with copyprop_hardreg_forward and shared RTX
Date: Mon, 04 Mar 2002 06:43:00 -0000 [thread overview]
Message-ID: <OF5642ED36.98F5EB04-ONC1256B72.005002A2@de.ibm.com> (raw)
Richard Henderson wrote:
>On Fri, Mar 01, 2002 at 04:58:53PM +0100, Ulrich Weigand wrote:
>> Am I missing something here? How is this supposed to work?
>
>There isn't supposed to be any shared rtx. That's the bug.
However, this appears to be done intentionally by reload,
if the comment at that place is to be believed:
The REG-rtx's for the pseudos are modified in place,
so all insns that used to refer to them now refer to memory.
So if this is the bug, do you have suggestions how to best fix it?
Simply make a pass through all insns and replace the rtx's where
necessary? Or something more involved like having these situations
handled by find_reloads (like the reg_equiv_address case)?
Mit freundlichen Gruessen / Best Regards
Ulrich Weigand
--
Dr. Ulrich Weigand
Linux for S/390 Design & Development
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
Phone: +49-7031/16-3727 --- Email: Ulrich.Weigand@de.ibm.com
next reply other threads:[~2002-03-04 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 6:43 Ulrich Weigand [this message]
2002-03-04 12:46 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 14:12 Ulrich Weigand
2002-03-06 14:19 ` Richard Henderson
2002-03-01 7:57 Ulrich Weigand
2002-03-01 9:47 ` Richard Henderson
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=OF5642ED36.98F5EB04-ONC1256B72.005002A2@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@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).