public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/43581] [4.5 Regression] exception handling broken across shared libaries Date: Tue, 30 Mar 2010 09:47:00 -0000 [thread overview] Message-ID: <20100330094648.5877.qmail@sourceware.org> (raw) In-Reply-To: <bug-43581-15771@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2010-03-30 09:46 ------- Works for me as well. Building GCC with --as-needed is known to at least break libjava big times (you can see that when testing). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43581
next prev parent reply other threads:[~2010-03-30 9:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-29 18:46 [Bug c++/43581] New: " rwild at gcc dot gnu dot org 2010-03-29 18:48 ` [Bug other/43581] [4.5 Regression] " pinskia at gcc dot gnu dot org 2010-03-29 20:43 ` pinskia at gcc dot gnu dot org 2010-03-30 9:47 ` rguenth at gcc dot gnu dot org [this message] 2010-03-30 13:56 ` rguenth at gcc dot gnu dot org 2010-03-30 16:58 ` [Bug other/43581] [4.5 Regression] exception handling broken across shared libaries with -fuse-linker-plugin rwild at gcc dot gnu dot org 2010-03-30 20:29 ` [Bug lto/43581] " pinskia at gcc dot gnu dot org 2010-03-31 9:23 ` rguenth at gcc dot gnu dot org 2010-03-31 18:50 ` rwild 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=20100330094648.5877.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: 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).