public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/40133] New: exception propagation support not enabled in libstdc++ 4.4 on {armeabi,hppa}-linux Date: Wed, 13 May 2009 16:54:00 -0000 [thread overview] Message-ID: <bug-40133-5724@http.gcc.gnu.org/bugzilla/> (raw) Tracking http://gcc.gnu.org/ml/gcc/2009-05/msg00035.html as a bug report. Paolo checked in a patch in rev 147123 on the gcc-4_4-branch to do link tests for the atomic builtins, which works ok on hppa, but fails for arm. -- Summary: exception propagation support not enabled in libstdc++ 4.4 on {armeabi,hppa}-linux Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: debian-gcc at lists dot debian dot org GCC target triplet: arm-linux-gnueabi hppa-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40133
next reply other threads:[~2009-05-13 16:54 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-13 16:54 debian-gcc at lists dot debian dot org [this message] 2009-05-13 17:07 ` [Bug libstdc++/40133] " debian-gcc at lists dot debian dot org 2009-05-13 18:42 ` paolo dot carlini at oracle dot com 2009-05-13 18:42 ` paolo dot carlini at oracle dot com 2009-05-17 18:42 ` pinskia at gcc dot gnu dot org 2009-05-22 10:07 ` mikpe at it dot uu dot se 2009-05-22 10:22 ` joseph at codesourcery dot com 2009-05-22 11:16 ` mikpe at it dot uu dot se 2009-05-22 13:36 ` ramana at gcc dot gnu dot org 2009-05-22 19:19 ` mikpe at it dot uu dot se 2009-05-22 20:30 ` paolo dot carlini at oracle dot com 2009-12-13 23:45 ` doko at gcc dot gnu dot org 2009-12-14 0:20 ` debian-gcc at lists dot debian 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-40133-5724@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).