From: chris@lslsun.epfl.ch (Christian Iseli)
To: law@cygnus.com, mengel@fsui02.FNAL.GOV
Cc: egcs@cygnus.com
Subject: Re: aix4.1 alias problem
Date: Thu, 06 Nov 1997 01:06:00 -0000 [thread overview]
Message-ID: <199711060906.KAA01420@lslsun17.epfl.ch> (raw)
> Well, it's the same basic problem as Christian ran into, except
> that the scheduler has moved things around in such a way that
> the copy out of the arg register appears after the function begin
> note.
>
> ...
>
> The other possibility is to set reg_seen for all the registers
> which might hold values at function entry. This might be overly
> pessimistic and defeat the entire purpose of tracking argument
> values for alias purposes. But should be 100% safe.
How about trying to do some clever walking through the reg_base_value
table, detecting cycles after the first loop iteration, and avoiding
to cycle during subsequent iterations of the loop?
Christian
reply other threads:[~1997-11-06 1:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199711060906.KAA01420@lslsun17.epfl.ch \
--to=chris@lslsun.epfl.ch \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=mengel@fsui02.FNAL.GOV \
/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).