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 target/29558] ICE in set_variable_part, at var-tracking.c:2140
Date: Mon, 23 Oct 2006 10:14:00 -0000	[thread overview]
Message-ID: <20061023101439.3468.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29558-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2006-10-23 10:14 -------
Slightly more reduced:

void stpi_unpack_16_1(int length, unsigned char *out, unsigned char bit)
{
  unsigned char tempin;
  unsigned char temp[16];
  for (bit = 128; length > 0; length--) {
    if (tempin & 128)
      temp[0] |= bit;
    else
      {
        *out++ = temp[1];
        *out++ = temp[2];
        *out++ = temp[3];
        *out++ = temp[4];
        *out++ = temp[5];
        *out++ = temp[6];
        *out++ = temp[7];
        *out++ = temp[9];
        *out++ = temp[10];
        *out++ = temp[11];
        *out++ = temp[12];
        *out++ = temp[13];
        *out++ = temp[14];
        *out++ = temp[15];
        __builtin_memset (temp, 0, 16);
     }
  }
}

it ICEs on

          /* We track only variables whose size is <= MAX_VAR_PARTS bytes
             thus there are at most MAX_VAR_PARTS different offsets.  */
          gcc_assert (var->n_var_parts < MAX_VAR_PARTS);

because var->n_var_parts is == MAX_VAR_PARTS.  It looks like the analysis
part is wrong in trying to track temp[].


-- 


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


  reply	other threads:[~2006-10-23 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23  9:07 [Bug target/29558] New: " rguenth at gcc dot gnu dot org
2006-10-23 10:14 ` rguenth at gcc dot gnu dot org [this message]
2006-10-23 11:29 ` [Bug target/29558] " rguenth at gcc dot gnu dot org
2006-10-23 15:48 ` [Bug middle-end/29558] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-10-23 16:06 ` [Bug debug/29558] " pinskia at gcc dot gnu dot org
2006-11-07 19:18 ` [Bug debug/29558] [4.2/4.3 " janis at gcc dot gnu dot org
2007-01-19 22:30 ` bergner at gcc dot gnu dot org
2007-01-19 22:32 ` bergner at gcc dot gnu dot org
2007-02-15 17:51 ` rth at gcc dot gnu dot org
2007-02-19 16:11 ` rth at gcc dot gnu dot org
2007-02-19 16:22 ` rth at gcc dot gnu dot org
2007-02-19 20:35 ` mmitchel at gcc dot gnu dot org
2007-02-19 23:45 ` rth 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=20061023101439.3468.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).