public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54868] New: gcc.dg/tree-ssa/forwprop-22.c FAILs
Date: Tue, 09 Oct 2012 09:11:00 -0000	[thread overview]
Message-ID: <bug-54868-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54868
           Summary: gcc.dg/tree-ssa/forwprop-22.c FAILs
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: glisse@gcc.gnu.org
              Host: i386-pc-solaris2.9, i686-unknown-linux-gnu
            Target: i386-pc-solaris2.9, i686-unknown-linux-gnu
             Build: i386-pc-solaris2.9, i686-unknown-linux-gnu


The new gcc.dg/tree-ssa/forwprop-22.c testcase FAILs on Solaris 9/x86 and
32-bit Linux/x86:

FAIL: gcc.dg/tree-ssa/forwprop-22.c scan-tree-dump-times copyprop1
"VEC_PERM_EXPR" 1
FAIL: gcc.dg/tree-ssa/forwprop-22.c scan-tree-dump-not copyprop1
"BIT_FIELD_REF"

  Rainer


             reply	other threads:[~2012-10-09  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  9:11 ro at gcc dot gnu.org [this message]
2012-10-09  9:12 ` [Bug tree-optimization/54868] " ro at gcc dot gnu.org
2012-10-09  9:58 ` [Bug tree-optimization/54868] [4.8 Regression]gcc.dg/tree-ssa/forwprop-22.c FAILs glisse at gcc dot gnu.org
2012-10-09 13:38 ` glisse at gcc dot gnu.org
2012-10-10  4:59 ` glisse at gcc dot gnu.org
2012-10-11  9:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-10-11  9:25 ` jakub at gcc dot gnu.org
2012-10-11  9:57 ` glisse at gcc dot gnu.org
2012-10-11 13:29 ` glisse at gcc dot gnu.org
2012-10-11 13:33 ` [Bug testsuite/54868] " 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-54868-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).