public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/43758]  New: [4.6 Regression] 19 new GCC HEAD@158360 regressions
Date: Thu, 15 Apr 2010 12:18:00 -0000	[thread overview]
Message-ID: <bug-43758-12313@http.gcc.gnu.org/bugzilla/> (raw)

Between revisions 158346 and 158360 the follwoing tests started to fail:

FAIL: g++.dg/ext/altivec-1.C (test for excess errors)
FAIL: g++.dg/ext/altivec-10.C (test for excess errors)
FAIL: g++.dg/ext/altivec-12.C (test for excess errors)
FAIL: g++.dg/ext/altivec-13.C (test for excess errors)
FAIL: g++.dg/ext/altivec-14.C (test for excess errors)
FAIL: g++.dg/ext/altivec-16.C (test for excess errors)
FAIL: g++.dg/ext/altivec-17.C  (test for errors, line 15)
FAIL: g++.dg/ext/altivec-17.C (test for excess errors)
FAIL: g++.dg/ext/altivec-2.C (test for excess errors)
FAIL: g++.dg/ext/altivec-3.C (test for excess errors)
FAIL: g++.dg/ext/altivec-4.C (test for excess errors)
FAIL: g++.dg/ext/altivec-5.C (test for excess errors)
FAIL: g++.dg/ext/altivec-6.C (test for excess errors)
FAIL: g++.dg/ext/altivec-7.C (test for excess errors)
ERROR: g++.dg/ext/altivec-7.C: error executing dg-final: couldn't open
"altivec-7.s": no such file or directory
UNRESOLVED: g++.dg/ext/altivec-7.C: error executing dg-final: couldn't open
"altivec-7.s": no such file or directory
FAIL: g++.dg/ext/altivec-8.C (test for excess errors)
FAIL: g++.dg/ext/altivec-9.C (test for excess errors)
FAIL: g++.dg/ext/altivec-cell-1.C (test for excess errors)
FAIL: g++.dg/ext/altivec-cell-2.C (test for excess errors)
FAIL: g++.dg/ext/altivec-cell-3.C (test for excess errors)
FAIL: g++.dg/ext/altivec-cell-4.C (test for excess errors)
FAIL: g++.dg/ext/altivec-cell-5.C (test for excess errors)

The errors are 

/opt/gcc/_gcc_clean/gcc/testsuite/g++.dg/ext/altivec-1.C:14:3: error:
'vector__' was not declared in this scope
/opt/gcc/_gcc_clean/gcc/testsuite/g++.dg/ext/altivec-1.C:15:3: error:
'vector__' was not declared in this scope

(see
http://gcc.gnu.org/regtest/HEAD/native-logsum/gcc/testsuite/g++/g++.log.gzip
for a full log).


-- 
           Summary: [4.6 Regression] 19 new GCC HEAD@158360 regressions
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: testsuite
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dominiq at lps dot ens dot fr
 GCC build triplet: powerpc-apple-darwin9
  GCC host triplet: powerpc-apple-darwin9
GCC target triplet: powerpc-apple-darwin9


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


             reply	other threads:[~2010-04-15 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 12:18 dominiq at lps dot ens dot fr [this message]
2010-04-15 12:51 ` [Bug testsuite/43758] " jakub at gcc dot gnu dot org
2010-04-15 12:56 ` rguenth at gcc dot gnu dot org
2010-04-19  9:17 ` dominiq at lps dot ens dot fr
2010-05-03 21:45 ` jason at gcc dot gnu dot org
2010-05-04  4:31 ` jason at gcc dot gnu dot org
2010-05-04  4:32 ` jason at gcc dot gnu dot org
2010-05-05 16:57 ` jason at gcc dot gnu dot org
2010-05-05 18:59 ` meissner at gcc dot gnu dot org
2010-05-05 19:34 ` jason at gcc dot gnu dot org
2010-05-05 19:57 ` jason at gcc dot gnu dot 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-43758-12313@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).