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 other/51822] New: libitm.c++/eh-1.C FAILs
Date: Wed, 11 Jan 2012 11:15:00 -0000	[thread overview]
Message-ID: <bug-51822-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51822
           Summary: libitm.c++/eh-1.C FAILs
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: aldyh@gcc.gnu.org
              Host: i386-pc-solaris2*
            Target: i386-pc-solaris2*
             Build: i386-pc-solaris2*


The libitm.c++/eh-1.C test FAILs on various Solaris/x86 configurations with

terminate called after throwing an instance of 'int'

The failure matrix is strange, though:

                     as, ld   gas, ld   gas, gld

Solaris 8            PASS     FAIL      FAIL
Solaris 9            PASS     FAIL      FAIL
Solaris 10, 32-bit   FAIL (1) FAIL      (2)
            64-bit   FAIL (1) FAIL      (2)
Solaris 11, 32-bit   FAIL (1) PASS      PASS
            64-bit   FAIL (1) FAIL      FAIL

(1) Those failures are unrelated, cf.
http://gcc.gnu.org/ml/gcc-patches/2011-11/msg02093.html.

(2) Doesn't currently bootstrap.

I'd have expected the gas, ld and gas, gld configurations to pass instead of
the as, ld onces since (unlike as) gas supports the .cfi* mnemonics in
config/x86/sjlj.S.

  Rainer


             reply	other threads:[~2012-01-11 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 11:15 ro at gcc dot gnu.org [this message]
2012-01-16 17:40 ` [Bug libitm/51822] " ro at gcc dot gnu.org
2012-01-31 12:49 ` ro 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-51822-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).