public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51583] New: One more missing force_gimple_operand in SRA
Date: Fri, 16 Dec 2011 16:57:00 -0000	[thread overview]
Message-ID: <bug-51583-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51583
           Summary: One more missing force_gimple_operand in SRA
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: jamborm@gcc.gnu.org
        ReportedBy: jamborm@gcc.gnu.org


Created attachment 26113
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26113
Testcase

I noticed that part of my fix to PR 50622 somehow got lost which can
lead to ICEs in some obscure cases, for example when compiling the
attached testcase.  It fails on i686 and x86_64, on both the trunk and
the 4.6 branch with:

test.c: In function ‘foo’:
test.c:34:1: error: invalid rhs for gimple memory store
s$u$v

t.u.v;

# .MEM_20 = VDEF <.MEM_14>
s$u$v = t.u.v;

test.c:34:1: internal compiler error: verify_stmts failed

I am about to bootstrap and test a fix.


             reply	other threads:[~2011-12-16 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 16:57 jamborm at gcc dot gnu.org [this message]
2011-12-17  3:06 ` [Bug tree-optimization/51583] " jamborm at gcc dot gnu.org
2011-12-19 14:34 ` jamborm at gcc dot gnu.org
2011-12-19 16:48 ` jamborm at gcc dot gnu.org
2011-12-20 11:24 ` jamborm 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-51583-4@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).