public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53693] [4.7/4.8 regression] ICE in vect_get_vec_def_for_stmt_copy, at tree-vect-stmts.c:1438
Date: Sat, 16 Jun 2012 15:01:00 -0000	[thread overview]
Message-ID: <bug-53693-4-Q2jApkQzDr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53693-4@http.gcc.gnu.org/bugzilla/>

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-06-16
   Target Milestone|---                         |4.7.3
            Summary|[4.7 regression] ICE in     |[4.7/4.8 regression] ICE in
                   |vect_get_vec_def_for_stmt_c |vect_get_vec_def_for_stmt_c
                   |opy, at                     |opy, at
                   |tree-vect-stmts.c:1438      |tree-vect-stmts.c:1438
     Ever Confirmed|0                           |1

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> 2012-06-16 15:01:03 UTC ---
It is caused by revision 177409:

http://gcc.gnu.org/ml/gcc-cvs/2011-08/msg00420.html


  reply	other threads:[~2012-06-16 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16  2:01 [Bug c++/53693] New: [4.7 " bearoso at gmail dot com
2012-06-16 15:01 ` hjl.tools at gmail dot com [this message]
2012-06-18  9:11 ` [Bug tree-optimization/53693] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-06-18 10:22 ` rguenth at gcc dot gnu.org
2012-06-18 10:56 ` rguenth at gcc dot gnu.org
2012-06-18 14:05 ` rguenth at gcc dot gnu.org
2012-06-18 14:11 ` [Bug tree-optimization/53693] [4.7 " rguenth at gcc dot gnu.org
2012-07-06  9:21 ` rguenth at gcc dot gnu.org
2012-07-06  9:26 ` rguenth 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-53693-4-Q2jApkQzDr@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).