public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18298] [4.0 Regression] bad code from lim ssa pass with strcmp
Date: Thu, 04 Nov 2004 20:25:00 -0000 [thread overview]
Message-ID: <20041104202508.15088.qmail@sourceware.org> (raw)
In-Reply-To: <20041104155905.18298.snyder@fnal.gov>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-04 20:25 -------
Adding a may_alias pass after fold all builtins makes this testcase works (I don't know if this is correct
fix or not):
Index: tree-optimize.c
===============================================================
====
RCS file: /cvs/gcc/gcc/gcc/tree-optimize.c,v
retrieving revision 2.61
diff -u -p -r2.61 tree-optimize.c
--- tree-optimize.c 2 Nov 2004 00:23:04 -0000 2.61
+++ tree-optimize.c 4 Nov 2004 20:23:32 -0000
@@ -371,6 +371,7 @@ init_tree_optimization_passes (void)
NEXT_PASS (pass_ccp);
NEXT_PASS (pass_redundant_phi);
NEXT_PASS (pass_fold_builtins);
+ NEXT_PASS (pass_may_alias);
NEXT_PASS (pass_split_crit_edges);
NEXT_PASS (pass_pre);
NEXT_PASS (pass_loop);
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18298
next prev parent reply other threads:[~2004-11-04 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 15:59 [Bug tree-optimization/18298] New: 4.0: " gcc-bugzilla at gcc dot gnu dot org
2004-11-04 16:06 ` [Bug tree-optimization/18298] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-04 16:19 ` dberlin at gcc dot gnu dot org
2004-11-04 18:04 ` pinskia at gcc dot gnu dot org
2004-11-04 20:25 ` pinskia at gcc dot gnu dot org [this message]
2004-11-29 23:01 ` dnovillo at gcc dot gnu dot org
2004-11-29 23:03 ` pinskia at gcc dot gnu dot org
2004-11-30 15:39 ` pinskia at gcc dot gnu dot org
2004-11-30 15:40 ` cvs-commit 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=20041104202508.15088.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).