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 middle-end/47048] misc vect.exp failures with -fgraphite-identity enabled at -O2.
Date: Tue, 01 Feb 2011 23:32:00 -0000	[thread overview]
Message-ID: <bug-47048-4-C8n67m98kG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47048-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Sebastian Pop <spop at gcc dot gnu.org> 2011-02-01 23:32:20 UTC ---
More specifically, the code that is now confused by the (int) cast is:

  dr_analyze_innermost (dr);
  dr_analyze_indices (dr, nest, loop);

in create_data_ref.


  parent reply	other threads:[~2011-02-01 23:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  4:06 [Bug middle-end/47048] New: " howarth at nitro dot med.uc.edu
2011-02-01 21:19 ` [Bug middle-end/47048] " howarth at nitro dot med.uc.edu
2011-02-01 21:27 ` spop at gcc dot gnu.org
2011-02-01 23:28 ` spop at gcc dot gnu.org
2011-02-01 23:32 ` spop at gcc dot gnu.org [this message]
2011-02-02  7:42 ` Joost.VandeVondele at pci dot uzh.ch
2011-02-07 12:35 ` howarth at nitro dot med.uc.edu
2011-07-29  1:55 ` howarth at nitro dot med.uc.edu
2024-04-03 23:00 ` pinskia 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-47048-4-C8n67m98kG@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).