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 middle-end/52656] New: [4.8 regression] gcc.target/sparc/fpmul-2.c FAILs
Date: Wed, 21 Mar 2012 15:51:00 -0000	[thread overview]
Message-ID: <bug-52656-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52656
           Summary: [4.8 regression] gcc.target/sparc/fpmul-2.c FAILs
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: ebotcazou@gcc.gnu.org, rguenth@gcc.gnu.org
              Host: sparc-sun-solaris2*
            Target: sparc-sun-solaris2*
             Build: sparc-sun-solaris2*


As initially mentioned in PR testsuite/52614, gcc.target/sparc/fpmul-2.c has
recently started to fail:

FAIL: gcc.target/sparc/fpmul-2.c scan-tree-dump optimized "{ 2, 4, 6, 8 }"

It turned out that the failure is unrelated to the other ones, and a reghunt
revealed the culprit patch:

2012-03-16  Richard Guenther  <rguenther@suse.de>

        * tree.h (TREE_VECTOR_CST_ELTS): Remove.
        (VECTOR_CST_NELTS, VECTOR_CST_ELTS, VECTOR_CST_ELT): New defines.
        (struct tree_vector): Remove elements member, add variable size
        elts array member.
        (build_vector_stat): Declare.
        (build_vector): Define in terms of build_vector_stat.
[...]
        * config/sparc/sparc.c (sparc_handle_vis_mul8x16): Adjust interface
        and implementation.
        (sparc_fold_builtin): Adjust.

Here's the change in the optimized dumps:

> diff -u 23[45]/gcc/fpmul-2.c*|more
--- 234/gcc/fpmul-2.c.149t.optimized    2012-03-21 14:58:58.358234100 +0100
+++ 235/gcc/fpmul-2.c.149t.optimized    2012-03-21 16:18:28.973592400 +0100
@@ -48,7 +48,7 @@
 foo3 ()
 {
 <bb 2>:
-  return { 2, 4, 6, 8 };
+  return { 1, 2, 3, 4 };

 }

  Rainer


             reply	other threads:[~2012-03-21 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 15:51 ro at gcc dot gnu.org [this message]
2012-03-21 15:54 ` [Bug middle-end/52656] " ebotcazou at gcc dot gnu.org
2012-03-22  7:24 ` rguenth at gcc dot gnu.org
2012-03-24 18:44 ` ebotcazou at gcc dot gnu.org
2012-03-24 18:48 ` ebotcazou 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-52656-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).