public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49260] New: cpp0x/lambda/lambda-eh2.C fails execution Date: Wed, 01 Jun 2011 17:28:00 -0000 [thread overview] Message-ID: <bug-49260-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49260 Summary: cpp0x/lambda/lambda-eh2.C fails execution Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: janis@gcc.gnu.org Test g++.dg/cpp0x/lambda/lambda-eh2.C fails execution on several targets as shown by archived test results: alpha-dec-osf5.1b arm-none-linux-gnueabi hppa2.0w-hp-hpux11.11 i686-apple-darwin9 powerpc-apple-darwin9.8.0 powerpc64-unknown-linux-gnu sh4-unknown-linux-gnu sparc-sun-solaris2.8, 2.9, 2.10 (but not 2.11) It also fails for arm-none-eabi, although the build has failed lately. Testing on arm-none-linux-gnueabi shows that the test has failed on that target since it was added on 2011-05-23 for r174076, to go with this fix: 2011-05-23 Jason Merrill <jason@redhat.com> PR c++/47263 * decl.c (use_eh_spec_block): Do use an EH spec block for a lambda op().
next reply other threads:[~2011-06-01 17:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-01 17:28 janis at gcc dot gnu.org [this message] 2011-06-01 17:32 ` [Bug c++/49260] " janis at gcc dot gnu.org 2011-06-02 22:41 ` dominiq at lps dot ens.fr 2011-06-06 10:09 ` ro at gcc dot gnu.org 2011-06-06 11:19 ` ebotcazou at gcc dot gnu.org 2011-06-20 14:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-06-20 15:57 ` ebotcazou at gcc dot gnu.org 2011-06-22 15:17 ` jason at gcc dot gnu.org 2011-06-22 15:56 ` jason at gcc dot gnu.org 2011-06-22 15:59 ` jason at gcc dot gnu.org 2011-06-28 7:15 ` [Bug c++/49260] [C++0x] lambda-eh2.C " ebotcazou at gcc dot gnu.org 2011-08-02 15:38 ` jason at gcc dot gnu.org 2011-08-02 18:33 ` jason 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-49260-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: linkBe 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).