public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Kyle.D.Moffett at boeing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/50988] New: gcc.target/powerpc/altivec-34.c: Test build failure on non-AltiVec targets
Date: Thu, 03 Nov 2011 20:31:00 -0000	[thread overview]
Message-ID: <bug-50988-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 50988
           Summary: gcc.target/powerpc/altivec-34.c: Test build failure on
                    non-AltiVec targets
    Classification: Unclassified
           Product: gcc
           Version: 4.6.2
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: Kyle.D.Moffett@boeing.com


All of the other AltiVec tests (except altivec-34.c) have:
  /* { dg-require-effective-target powerpc_altivec_ok } */

As a result, a bogus testcase failure is generated on powerpc-linux-gnuspe:
  FAIL: gcc.target/powerpc/altivec-34.c (test for excess errors)
  Excess errors:
 
/srv/build/kmoffett/gcc-4.6-4.6.2/src/gcc/testsuite/gcc.target/powerpc/altivec-34.c:1:0:
error: AltiVec and E500 instructions cannot coexist

Cheers,
Kyle Moffett

--
Curious about my work on the Debian powerpcspe port?
I'm keeping a blog here: http://pureperl.blogspot.com/


             reply	other threads:[~2011-11-03 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 20:31 Kyle.D.Moffett at boeing dot com [this message]
2011-11-03 20:44 ` [Bug testsuite/50988] " Kyle.D.Moffett at boeing dot com
2011-12-28 22:31 ` [Bug testsuite/50988] gcc.target/powerpc/*: Several tests fail incorrectly on powerpc-linux-gnuspe meissner at gcc dot gnu.org
2011-12-28 22:32 ` meissner at gcc dot gnu.org
2011-12-28 22:40 ` meissner at gcc dot gnu.org
2011-12-29 19:20 ` meissner 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-50988-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).