From: Jim Wilson <wilson@tuliptree.org>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: gcc@gcc.gnu.org, rth@redhat.com
Subject: Re: Redundant check for prologue_epilogue_contains in init_alias_analysis?
Date: Sun, 07 Sep 2003 19:42:00 -0000 [thread overview]
Message-ID: <1062963418.1030.10.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <20030907095936.GA4527@atrey.karlin.mff.cuni.cz>
On Sun, 2003-09-07 at 02:59, Zdenek Dvorak wrote:
> would then just forcing fp to be considered a constant base pointer
> unconditionally be a solution?
That could work if there is no target that ever modifies FP during the
function, and if we can safely distinguish between real uses of the FP,
and cases where the FP was used by the register allocator. This seems
likely to be true.
Another possible solution is to disregard instructions that modify FP if
they are prologue/epilogue instructions. This seems safer, but is a bit
more code.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
prev parent reply other threads:[~2003-09-07 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 17:34 Zdenek Dvorak
2003-09-07 3:59 ` Jim Wilson
2003-09-07 10:39 ` Zdenek Dvorak
2003-09-07 19:42 ` Jim Wilson [this message]
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=1062963418.1030.10.camel@leaf.tuliptree.org \
--to=wilson@tuliptree.org \
--cc=gcc@gcc.gnu.org \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
--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).