public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "spop at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46928] data dependence analysis fails on constant array accesses
Date: Mon, 13 Dec 2010 18:09:00 -0000	[thread overview]
Message-ID: <bug-46928-4-W3RAxzIXz0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46928-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46928

Sebastian Pop <spop at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2010.12.13 18:09:36
         AssignedTo|unassigned at gcc dot       |spop at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #1 from Sebastian Pop <spop at gcc dot gnu.org> 2010-12-13 18:09:36 UTC ---
Mine.

BTW, this PR comes from example 2 of http://blog.regehr.org/archives/320


  reply	other threads:[~2010-12-13 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 18:06 [Bug tree-optimization/46928] New: " spop at gcc dot gnu.org
2010-12-13 18:09 ` spop at gcc dot gnu.org [this message]
2010-12-13 18:38 ` [Bug tree-optimization/46928] " xinliangli at gmail dot com
2010-12-13 18:59 ` spop at gcc dot gnu.org
2010-12-13 19:06 ` sebpop at gmail dot com
2010-12-13 19:30 ` spop at gcc dot gnu.org
2010-12-15  5:05 ` spop at gcc dot gnu.org
2010-12-15  5:07 ` spop at gcc dot gnu.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=bug-46928-4-W3RAxzIXz0@http.gcc.gnu.org/bugzilla/ \
    --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).