public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dogcow at babymeat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/26489] [4.1/4.2 Regression] compilation of c++ fails in eh_alloc.cc on NetBSD
Date: Tue, 28 Feb 2006 07:42:00 -0000	[thread overview]
Message-ID: <20060228064533.26748.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26489-12278@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from dogcow at babymeat dot com  2006-02-28 06:45 -------
results sent to gcc-testresults; here's the summary of the g++ section of the
tests.

FAIL: g++.dg/init/array15.C execution test
XPASS: g++.dg/tree-ssa/pr14814.C scan-tree-dump-times &this 0
XPASS: g++.old-deja/g++.other/init5.C execution test

                === g++ Summary ===

# of expected passes            11965
# of unexpected failures        1
# of unexpected successes       2
# of expected failures          66
# of unsupported tests          86
/aux/obj/gcc41/gcc/testsuite/../g++  version 4.1.0 20060228 (prerelease)

Running target unix
FAIL: 26_numerics/cmath/c99_classification_macros_c++.cc (test for excess
errors)
FAIL: 26_numerics/cmath/c99_classification_macros_c.cc (test for excess errors)

                === libstdc++ Summary ===

# of expected passes            2641
# of unexpected failures        2
# of expected failures          10
# of unsupported tests          147


-- 


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


  parent reply	other threads:[~2006-02-28  6:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 23:01 [Bug c++/26489] New: " dogcow at babymeat dot com
2006-02-27 23:09 ` [Bug libstdc++/26489] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-28  0:08 ` dogcow at babymeat dot com
2006-02-28  1:10 ` pcarlini at suse dot de
2006-02-28  1:27 ` [Bug other/26489] " pinskia at gcc dot gnu dot org
2006-02-28  1:34 ` dogcow at babymeat dot com
2006-02-28  1:45 ` pinskia at gcc dot gnu dot org
2006-02-28  1:47 ` dogcow at babymeat dot com
2006-02-28  2:00 ` pinskia at gcc dot gnu dot org
2006-02-28  2:07 ` pinskia at gcc dot gnu dot org
2006-02-28  2:11 ` roger at eyesopen dot com
2006-02-28  3:23 ` dogcow at babymeat dot com
2006-02-28  3:25 ` roger at eyesopen dot com
2006-02-28  6:45 ` roger at eyesopen dot com
2006-02-28  7:42 ` dogcow at babymeat dot com [this message]
2006-02-28 20:49 ` mmitchel at gcc dot gnu dot org
2006-03-02  2:14 ` dogcow at babymeat dot com
2006-03-02  2:47 ` sayle at gcc dot gnu dot org
2006-03-02  3:27 ` [Bug other/26489] [4.1 " pinskia at gcc dot gnu dot org
2006-03-14 19:21 ` sayle at gcc dot gnu dot org
2006-03-14 23:08 ` pinskia 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=20060228064533.26748.qmail@sourceware.org \
    --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).