From: Richard Henderson <rth@redhat.com>
To: dalej@apple.com
Cc: gcc@gcc.gnu.org
Subject: Re: how to fix anti-optimization?
Date: Wed, 12 Sep 2001 15:14:00 -0000 [thread overview]
Message-ID: <20010912151445.A13526@redhat.com> (raw)
In-Reply-To: <200109121834.LAA21595@scv1.apple.com>
On Wed, Sep 12, 2001 at 11:35:00AM -0700, dalej@apple.com wrote:
> The substitution is done in the ARRAY_REF case of expr.c:expand_expr().
> It looks like I could hack this by setting TREE_SIDE_EFFECTS on FP
> constants, but surely that's not the right way to do it. Any better ideas?
If the constant is not LEGITIMATE_CONSTANT_P, make the ARRAY_REF
expand as normal, then tag the resulting memory reference with a
REG_EQUAL note containing the known constant.
r~
next prev parent reply other threads:[~2001-09-12 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 11:34 dalej
2001-09-12 15:14 ` Richard Henderson [this message]
2001-09-14 12:50 ` Dale Johannesen
2001-09-14 13:02 ` David Edelsohn
2001-09-14 13:36 ` Richard Henderson
2001-09-13 10:50 ` David Edelsohn
2001-09-13 11:03 ` Dale Johannesen
2001-09-14 15:27 Richard Kenner
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=20010912151445.A13526@redhat.com \
--to=rth@redhat.com \
--cc=dalej@apple.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).