public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/55167] [4.8 Regression]: g++.dg/other/vector-compare.C, ICE
Date: Thu, 01 Nov 2012 19:05:00 -0000	[thread overview]
Message-ID: <bug-55167-4-YCYICjVDym@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55167-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> 2012-11-01 19:05:13 UTC ---
Thanks.

Since the error happens in expand, I assume this is a dup of PR 55001, for
which I posted a patch earlier today. Note that AFAIK, anything that starts
failing because of this patch was silently miscompiled before.

(I am also investigating a different problem with this testcase, due to the
fact that the C front-end turns (void)(x<0) into if(x<0)(void)0 which vector x
doesn't like)


  reply	other threads:[~2012-11-01 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 18:47 [Bug regression/55167] New: " hp at gcc dot gnu.org
2012-11-01 19:05 ` glisse at gcc dot gnu.org [this message]
2012-11-01 19:52 ` [Bug regression/55167] " hp at gcc dot gnu.org
2012-11-01 20:22 ` glisse at gcc dot gnu.org
2012-11-02  5:34 ` hp at gcc dot gnu.org
2012-11-02  8:31 ` glisse 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-55167-4-YCYICjVDym@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).