From: Jason Merrill <jason_merrill@redhat.com>
To: Jan Hubicka <jh@suse.cz>
Cc: Mark Mitchell <mark@codesourcery.com>,
Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: spec2000 regression
Date: Thu, 16 Aug 2001 06:09:00 -0000 [thread overview]
Message-ID: <m37kw4due7.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <20010816145745.J14857@atrey.karlin.mff.cuni.cz>
>>>>> "Jan" == Jan Hubicka <jh@suse.cz> writes:
> + /* set_mem_attributes uses DECL_RTL to avoid re-generating of
> + already computed alias sets. Here we want to re-generate. */
> + if (TREE_CODE (decl) != SAVE_EXPR)
> + SET_DECL_RTL (decl, NULL);
> set_mem_attributes (reg, decl, 1);
> + if (TREE_CODE (decl) != SAVE_EXPR)
> + SET_DECL_RTL (decl, reg);
This should check DECL_P. Otherwise, looks good.
Jason
next prev parent reply other threads:[~2001-08-16 6:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 5:57 Richard Kenner
2001-08-15 6:03 ` Jan Hubicka
2001-08-15 6:36 ` Jason Merrill
2001-08-15 6:52 ` Jan Hubicka
2001-08-15 7:11 ` Jason Merrill
2001-08-15 7:13 ` Jan Hubicka
2001-08-15 7:36 ` Jan Hubicka
2001-08-15 8:04 ` Mark Mitchell
2001-08-16 5:58 ` Jan Hubicka
2001-08-16 6:09 ` Jason Merrill [this message]
2001-08-16 7:40 ` Jan Hubicka
2001-08-16 7:46 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 11:28 Richard Kenner
2001-08-16 6:09 ` Jason Merrill
2001-08-22 7:53 ` Jason Merrill
2001-08-15 7:08 Richard Kenner
2001-08-15 7:10 ` Jan Hubicka
[not found] <20010815123730.P19872@atrey.karlin.mff.cuni.cz>
[not found] ` <m366bpsi91.fsf@prospero.cambridge.redhat.com>
2001-08-15 5:41 ` Jan Hubicka
2001-08-15 6:18 ` Jason Merrill
2001-08-15 6:40 ` Joseph S. Myers
2001-08-15 7:36 ` Jan Hubicka
2001-08-15 7:44 ` Joseph S. Myers
2001-08-15 11:04 ` Andreas Jaeger
2001-08-15 7:56 ` Mark Mitchell
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=m37kw4due7.fsf@prospero.cambridge.redhat.com \
--to=jason_merrill@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=mark@codesourcery.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).