public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37861] Bogus array bounds warning
Date: Thu, 30 Oct 2008 17:46:00 -0000	[thread overview]
Message-ID: <20081030174352.8518.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37861-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from jamborm at gcc dot gnu dot org  2008-10-30 17:43 -------
Well, yes, we do generate that code.  However, the loop is unrolled
later on and the IR code on which the vrp complains later on actually is:

main ()
{
  unsigned int ivtmp.27;
  unsigned int pretmp.17;
  int pretmp.16;
  unsigned int pretmp.15;
  unsigned int anz.0;
  unsigned int D.1258;
  char * D.1259;
  int anz;

  # BLOCK 2 freq:909
  # PRED: ENTRY [100.0%]  (fallthru,exec)
  D.1259_28 = &formatstr[0][0];
  printf (&"%d %s\n"[0], 0, D.1259_28);
  D.1259_39 = &formatstr[0][100];
  printf (&"%d %s\n"[0], 1, D.1259_39);
  D.1259_50 = &formatstr[0][200];
  printf (&"%d %s\n"[0], 2, D.1259_50);
  D.1259_61 = &formatstr[0][300];
  printf (&"%d %s\n"[0], 3, D.1259_61);
  D.1259_72 = &formatstr[0][400];
  printf (&"%d %s\n"[0], 4, D.1259_72);
  D.1259_83 = &formatstr[0][500];
  printf (&"%d %s\n"[0], 5, D.1259_83);
  D.1259_94 = &formatstr[0][600];
  printf (&"%d %s\n"[0], 6, D.1259_94);
  D.1259_105 = &formatstr[0][700];
  printf (&"%d %s\n"[0], 7, D.1259_105);
  D.1259_116 = &formatstr[0][800];
  printf (&"%d %s\n"[0], 8, D.1259_116);
  D.1259_7 = &formatstr[0][900];
  printf (&"%d %s\n"[0], 9, D.1259_7);
  printf (&"   %d\n"[0], 10);
  return 0;
  # SUCC: EXIT [100.0%] 

}


-- 


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


  reply	other threads:[~2008-10-30 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  8:27 [Bug middle-end/37861] New: " rguenth at gcc dot gnu dot org
2008-10-30 17:46 ` jamborm at gcc dot gnu dot org [this message]
2008-10-30 18:45 ` [Bug middle-end/37861] " manu at gcc dot gnu dot org
2008-10-31 17:54 ` jamborm at gcc dot gnu dot org
2008-10-31 18:02 ` jamborm at gcc dot gnu dot org
2008-11-04 15:52 ` jamborm at gcc dot gnu dot org
2008-11-05  9:56 ` [Bug middle-end/37861] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2008-11-05 16:09 ` jamborm at gcc dot gnu dot org
2008-11-05 20:51 ` [Bug middle-end/37861] [4.3 " jakub at gcc dot gnu dot org
2008-11-10 10:07 ` jamborm at gcc dot gnu dot org
2008-11-10 18:41 ` jamborm at gcc dot gnu dot org
2008-11-15  0:01 ` pinskia at gcc dot gnu dot org
2008-11-30 23:02 ` rguenth at gcc dot gnu dot org
2008-12-02 14:34 ` jamborm at gcc dot gnu dot org
2009-01-24 10:26 ` rguenth at gcc dot gnu dot org
2009-02-28  0:31 ` jamborm at gcc dot gnu dot org
2009-02-28 18:33 ` jamborm at gcc dot gnu dot org
2009-02-28 22:46 ` jamborm 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=20081030174352.8518.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).