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 target/46880] [4.4/4.5/4.6 Regression] generating of shufpd is broken
Date: Sat, 18 Dec 2010 23:17:00 -0000	[thread overview]
Message-ID: <bug-46880-4-wkWreJJZG1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46880-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2010.12.18 23:16:58
                 CC|                            |vmakarov at redhat dot com
     Ever Confirmed|0                           |1

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> 2010-12-18 23:16:58 UTC ---
This is caused by revision 167519:

http://gcc.gnu.org/ml/gcc-cvs/2010-12/msg00200.html


  parent reply	other threads:[~2010-12-18 23:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10  2:23 [Bug tree-optimization/46880] New: [4.6 Regression] g++.dg/other/pr40446.C FAILs with custom flags zsojka at seznam dot cz
2010-12-10 13:26 ` [Bug tree-optimization/46880] " rguenth at gcc dot gnu.org
2010-12-18 21:33 ` zsojka at seznam dot cz
2010-12-18 22:05 ` [Bug target/46880] [4.4/4.5/4.6 Regression] generating of shufpd is broken zsojka at seznam dot cz
2010-12-18 23:17 ` hjl.tools at gmail dot com [this message]
2010-12-21 14:21 ` jakub at gcc dot gnu.org
2010-12-21 14:45 ` jakub at gcc dot gnu.org
2010-12-21 22:37 ` jakub at gcc dot gnu.org
2010-12-21 22:39 ` [Bug target/46880] [4.4/4.5 " jakub at gcc dot gnu.org
2011-01-16 20:32 ` jakub at gcc dot gnu.org
2011-01-17  0:38 ` jakub at gcc dot gnu.org
2011-01-17  8:05 ` jakub at gcc dot gnu.org
2011-01-17 12:06 ` 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-46880-4-wkWreJJZG1@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).