public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/32328] [4.2/4.3 Regression] -fstrict-aliasing causes skipped code
Date: Wed, 20 Jun 2007 15:16:00 -0000 [thread overview]
Message-ID: <20070620151637.8984.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32328-14702@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from rguenth at gcc dot gnu dot org 2007-06-20 15:16 -------
trunk has the same problem, but different constraints:
Constraints:
ANYTHING = &ANYTHING
READONLY = &ANYTHING
INTEGER = &ANYTHING
barptr = &bar1
barptr.0_1 = barptr
Points-to sets
NULL = { }
ANYTHING = { ANYTHING }
READONLY = { ANYTHING }
INTEGER = { ANYTHING }
barptr = { bar1 }
bar1 = { }
barptr.0_1 = same as barptr
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |4.1.2
Summary|[4.2 Regression] -fstrict- |[4.2/4.3 Regression] -
|aliasing causes skipped code|fstrict-aliasing causes
| |skipped code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32328
next prev parent reply other threads:[~2007-06-20 15:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 21:18 [Bug c/32328] New: 4.2.0: -O2 " tdragon at tdragon dot net
2007-06-13 21:20 ` [Bug c/32328] " tdragon at tdragon dot net
2007-06-13 22:21 ` [Bug rtl-optimization/32328] " pinskia at gcc dot gnu dot org
2007-06-13 22:27 ` [Bug tree-optimization/32328] " tdragon at tdragon dot net
2007-06-13 22:36 ` tdragon at tdragon dot net
2007-06-13 22:47 ` tdragon at tdragon dot net
2007-06-20 14:45 ` tdragon at tdragon dot net
2007-06-20 14:47 ` tdragon at tdragon dot net
2007-06-20 14:52 ` tdragon at tdragon dot net
2007-06-20 15:13 ` [Bug tree-optimization/32328] [4.2 Regression] -fstrict-aliasing " rguenth at gcc dot gnu dot org
2007-06-20 15:16 ` rguenth at gcc dot gnu dot org [this message]
2007-06-20 15:36 ` [Bug tree-optimization/32328] [4.2/4.3 " tdragon at tdragon dot net
2007-06-20 20:04 ` dberlin at dberlin dot org
2007-06-20 20:09 ` dberlin at gcc dot gnu dot org
2007-07-04 3:29 ` mmitchel at gcc dot gnu dot org
2007-07-04 14:16 ` Daniel Berlin
2007-07-04 14:17 ` dberlin at dberlin dot org
2007-07-16 13:39 ` giovannibajo at libero dot it
2007-07-16 13:58 ` dberlin at dberlin dot org
2007-07-16 14:27 ` rguenth at gcc dot gnu dot org
2007-07-16 15:51 ` rguenth at gcc dot gnu dot org
2007-07-16 22:29 ` dberlin at dberlin dot org
2007-07-20 3:50 ` mmitchel at gcc dot gnu dot org
2007-08-19 23:24 ` dberlin at gcc dot gnu dot org
2007-08-20 1:54 ` dberlin at gcc dot gnu dot org
2007-08-22 15:52 ` rguenth at gcc dot gnu dot org
2007-08-23 12:42 ` [Bug tree-optimization/32328] [4.2 " rguenth at gcc dot gnu dot org
2007-09-05 6:47 ` giovannibajo at libero dot it
2007-09-05 8:29 ` rguenth at gcc dot gnu dot org
2007-09-05 11:51 ` dberlin at dberlin dot org
2007-10-09 19:30 ` mmitchel at gcc dot gnu dot org
2008-02-01 17:05 ` jsm28 at gcc dot gnu dot org
2008-02-22 18:15 ` tdragon at tdragon dot net
2008-02-22 18:48 ` pinskia at gcc dot gnu dot org
2008-05-19 20:27 ` jsm28 at gcc dot gnu dot org
2009-03-30 22:07 ` jsm28 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=20070620151637.8984.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).