public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/16967] Iterating gcse.c CPROP and PRE does not reach a fixed point
Date: Tue, 10 Aug 2004 16:25:00 -0000 [thread overview]
Message-ID: <20040810162551.11228.qmail@sourceware.org> (raw)
In-Reply-To: <20040810151043.16967.steven@gcc.gnu.org>
------- Additional Comments From steven at gcc dot gnu dot org 2004-08-10 16:25 -------
Apparently we don't want to GCSE a SYMBOL_REF because we already treat
them as constants for constant propagation.
Index: gcse.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/gcse.c,v
retrieving revision 1.309
diff -c -3 -p -r1.309 gcse.c
*** gcse.c 9 Aug 2004 16:58:42 -0000 1.309
--- gcse.c 10 Aug 2004 16:24:33 -0000
*************** want_to_gcse_p (rtx x)
*** 1214,1219 ****
--- 1214,1220 ----
{
case REG:
case SUBREG:
+ case SYMBOL_REF:
case CONST_INT:
case CONST_DOUBLE:
case CONST_VECTOR:
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16967
next prev parent reply other threads:[~2004-08-10 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 15:10 [Bug middle-end/16967] New: " steven at gcc dot gnu dot org
2004-08-10 15:34 ` [Bug rtl-optimization/16967] " pinskia at gcc dot gnu dot org
2004-08-10 15:36 ` steven at gcc dot gnu dot org
2004-08-10 15:54 ` steven at gcc dot gnu dot org
2004-08-10 16:25 ` steven at gcc dot gnu dot org [this message]
2004-08-10 21:47 ` pinskia at gcc dot gnu dot org
2005-05-04 1:16 ` dberlin at gcc dot gnu dot org
2005-05-04 23:03 ` steven at gcc dot gnu dot org
[not found] <bug-16967-280@http.gcc.gnu.org/bugzilla/>
2006-04-20 20:53 ` steven at gcc dot gnu dot org
2006-04-20 21:13 ` steven at gcc dot gnu dot org
2006-04-20 21:14 ` steven at gcc dot gnu dot org
2006-04-20 21:15 ` steven at gcc dot gnu dot org
2006-04-20 21:16 ` steven at gcc dot gnu dot org
2007-11-14 10:02 ` steven at gcc dot gnu dot org
2008-05-24 15:38 ` steven at gcc dot gnu dot org
2008-09-21 13:16 ` steven at gcc dot gnu dot org
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=20040810162551.11228.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).