public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "macro@linux-mips.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/63177] New: Power/Linux no-vfa-vect-depend-2.c and no-vfa-vect-depend-3.c failures
Date: Thu, 04 Sep 2014 17:16:00 -0000	[thread overview]
Message-ID: <bug-63177-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63177

            Bug ID: 63177
           Summary: Power/Linux no-vfa-vect-depend-2.c and
                    no-vfa-vect-depend-3.c failures
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
          Assignee: unassigned at gcc dot gnu.org
          Reporter: macro@linux-mips.org
              Host: i686-linux-gnu
            Target: powerpc-linux-gnu

I see these failures in 4.9/trunk Power/Linux testing:

FAIL: gcc.dg/vect/no-vfa-vect-depend-2.c scan-tree-dump-times vect "vectorized
1 loops" 1
FAIL: gcc.dg/vect/no-vfa-vect-depend-3.c scan-tree-dump-times vect "vectorized
1 loops" 4

These are new test cases as of 4.9.  Only seen with AltiVec multilibs:

-mcpu=603e
-mcpu=603e -msoft-float
-mcpu=7400 -maltivec -mabi=altivec
-mcpu=e6500 -maltivec -mabi=altivec
-mcpu=e6500 -m64 -maltivec -mabi=altivec

Options used to configure the compiler:

--build=i686-pc-linux-gnu
--target=powerpc-linux-gnu
--with-cpu-32=603e
--with-cpu-64=e5500
--with-long-double-128


             reply	other threads:[~2014-09-04 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 17:16 macro@linux-mips.org [this message]
2014-09-04 18:07 ` [Bug regression/63177] Powerpc " dominiq at lps dot ens.fr
2014-09-04 18:23 ` dominiq at lps dot ens.fr
2014-09-05  8:45 ` rguenth at gcc dot gnu.org
2018-06-06 18:47 ` [Bug target/63177] " bergner 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-63177-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).