public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc++/41430]  New: [4.5 Regression] exception handling testsuite failures in objc++
Date: Mon, 21 Sep 2009 15:20:00 -0000	[thread overview]
Message-ID: <bug-41430-578@http.gcc.gnu.org/bugzilla/> (raw)

Somewhere between mainline revisions 151661 and 151676 I started getting new
testsuite failures from objc++ as shown here:

Clean: http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg01158.html
FAIL: http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg01244.html

The new failures are:

FAIL: obj-c++.dg/except-1.mm execution test
FAIL: obj-c++.dg/try-catch-1.mm (internal compiler error)
FAIL: obj-c++.dg/try-catch-1.mm (test for excess errors)
FAIL: obj-c++.dg/try-catch-2.mm (test for excess errors)
FAIL: obj-c++.dg/try-catch-4.mm (internal compiler error)
FAIL: obj-c++.dg/try-catch-4.mm (test for excess errors)


-- 
           Summary: [4.5 Regression] exception handling testsuite failures
                    in objc++
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: EH
          Severity: normal
          Priority: P3
         Component: objc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ghazi at gcc dot gnu dot org
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2009-09-21 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 15:20 ghazi at gcc dot gnu dot org [this message]
2009-09-21 15:59 ` [Bug objc++/41430] " rguenth at gcc dot gnu dot org
2009-09-22 13:49 ` rguenth at gcc dot gnu dot org
2009-09-22 13:56 ` rguenth 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-41430-578@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).