From: Richard Henderson <rth@redhat.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Bug with copyprop_hardreg_forward and shared RTX
Date: Mon, 04 Mar 2002 12:46:00 -0000 [thread overview]
Message-ID: <20020304124632.A6719@redhat.com> (raw)
In-Reply-To: <OF5642ED36.98F5EB04-ONC1256B72.005002A2@de.ibm.com>; from Ulrich.Weigand@de.ibm.com on Mon, Mar 04, 2002 at 03:44:43PM +0100
On Mon, Mar 04, 2002 at 03:44:43PM +0100, Ulrich Weigand wrote:
> 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?
Hum. True, I'd forgotten about that sharing. I'd have thought in
general such substitutions would end up using the stack pointer or
the frame pointer, and so wouldn't end up being optimized.
I guess we could run an unshare_all_rtl_again pass after reload is
done...
r~
next prev parent reply other threads:[~2002-03-04 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 6:43 Ulrich Weigand
2002-03-04 12:46 ` Richard Henderson [this message]
-- 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=20020304124632.A6719@redhat.com \
--to=rth@redhat.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gcc@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).