public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59037] [4.8/4.9 Regression] ICE when accessing invalid element (nelts + 1) of vector
Date: Sun, 24 Nov 2013 18:50:00 -0000	[thread overview]
Message-ID: <bug-59037-4-k6bIebpBea@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59037-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from vries at gcc dot gnu.org ---
Created attachment 31286
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31286&action=edit
tentative patch

> I think it would be even better to fix whatever created that
> BIT_FIELD_REF, if you are motivated (though your patch isn't wrong)

This patch fixes the locations indicated by Matthew in comment 1.

For both c and c++, the testcase is fixed by the change in gimple-fold.c. The
other locations look like they need fixing too though, so I've included those
as well.

> Add a comment here explaining why this isn't an assert?

I've changed it into an assert.

I'll test this patch.


  parent reply	other threads:[~2013-11-24 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 12:29 [Bug middle-end/59037] New: " matthew.leach at arm dot com
2013-11-07 12:31 ` [Bug middle-end/59037] " matthew.leach at arm dot com
2013-11-07 12:32 ` jgreenhalgh at gcc dot gnu.org
2013-11-07 14:55 ` [Bug middle-end/59037] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-11-07 20:08 ` glisse at gcc dot gnu.org
2013-11-10  7:35 ` vries at gcc dot gnu.org
2013-11-10  8:34 ` glisse at gcc dot gnu.org
2013-11-24 18:50 ` vries at gcc dot gnu.org [this message]
2013-11-27 10:00 ` vries at gcc dot gnu.org
2013-12-02  8:37 ` vries at gcc dot gnu.org
2013-12-02  8:46 ` vries 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-59037-4-k6bIebpBea@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).