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 middle-end/32273] 'restrict' is forgotten after loop unrolling
Date: Mon, 11 Jun 2007 00:22:00 -0000 [thread overview]
Message-ID: <20070611002157.6569.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32273-14680@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at gcc dot gnu dot org 2007-06-11 00:21 -------
Yes this is fixed on the pointer_plus branch, the pointer_plus branch is better
at keeping track of what the decl is the restrict pointer's base.
-;; *D.1537 = *D.1539 + *D.1537
+;; *D.1538 = *D.1541 + *D.1538
(insn 14 13 15 t.c:16 (set (reg:SI 66)
- (mem:SI (reg:SI 59 [ D.1539 ]) [8 S4 A32])) -1 (nil)
+ (mem:SI (reg:SI 59 [ D.1541 ]) [2 S4 A32])) -1 (nil)
(nil))
(insn 15 14 0 t.c:16 (parallel [
- (set (mem:SI (reg:SI 60 [ D.1537 ]) [7 S4 A32])
- (plus:SI (mem:SI (reg:SI 60 [ D.1537 ]) [7 S4 A32])
+ (set (mem:SI (reg:SI 60 [ D.1538 ]) [2 S4 A32])
+ (plus:SI (mem:SI (reg:SI 60 [ D.1538 ]) [2 S4 A32])
(reg:SI 66)))
(clobber (reg:CC 17 flags))
]) -1 (nil)
- (expr_list:REG_EQUAL (plus:SI (mem:SI (reg:SI 60 [ D.1537 ]) [7 S4 A32])
- (mem:SI (reg:SI 59 [ D.1539 ]) [8 S4 A32]))
+ (expr_list:REG_EQUAL (plus:SI (mem:SI (reg:SI 60 [ D.1538 ]) [2 S4 A32])
+ (mem:SI (reg:SI 59 [ D.1541 ]) [2 S4 A32]))
(nil)))
See how the - has different aliasing sets than the +, the - has the correct
aliasing set.
So this is now mine.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |pinskia at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
GCC build triplet|i686-pc-linux-gnu |
GCC host triplet|i686-pc-linux-gnu |
GCC target triplet|i686-pc-linux-gnu |
Last reconfirmed|0000-00-00 00:00:00 |2007-06-11 00:21:57
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32273
next prev parent reply other threads:[~2007-06-11 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 14:47 [Bug c/32273] New: " tomash dot brechko at gmail dot com
2007-06-10 20:07 ` [Bug middle-end/32273] " rguenth at gcc dot gnu dot org
2007-06-10 22:41 ` dberlin at gcc dot gnu dot org
2007-06-10 22:55 ` pinskia at gcc dot gnu dot org
2007-06-11 0:22 ` pinskia at gcc dot gnu dot org [this message]
2007-06-16 5:49 ` [Bug tree-optimization/32273] " pinskia at gcc dot gnu dot org
2007-06-24 3:38 ` pinskia at gcc dot gnu dot org
2008-10-01 14:37 ` rguenth 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=20070611002157.6569.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).