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/19347] Invariant load not moved out of loop
Date: Fri, 03 Apr 2009 12:06:00 -0000	[thread overview]
Message-ID: <20090403120636.13801.qmail@sourceware.org> (raw)
In-Reply-To: <bug-19347-9531@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rguenth at gcc dot gnu dot org  2009-04-03 12:06 -------
The store to *ptr aliases the load from osmesa->clearpixel - there
is no (easy) way to otherwise prove that it is not (at least with the
testcase).
We do not see where osmesa->buffer points to (it may point to
&osmesa->clearpixel).


-- 


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


  parent reply	other threads:[~2009-04-03 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19347-9531@http.gcc.gnu.org/bugzilla/>
2005-10-24  0:20 ` pinskia at gcc dot gnu dot org
2009-04-03 12:06 ` rguenth at gcc dot gnu dot org [this message]
     [not found] <bug-19347-4@http.gcc.gnu.org/bugzilla/>
2024-01-03 19:14 ` phosit at autistici dot org
2024-01-03 19:35 ` phosit at autistici dot org
2005-01-09 10:51 [Bug tree-optimization/19347] New: " irar at il dot ibm dot com
2005-01-09 15:55 ` [Bug tree-optimization/19347] " pinskia at gcc dot gnu dot org
2005-04-11  6:10 ` pinskia 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=20090403120636.13801.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).