public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/35222] [4.3/4.4 Regression] EH output contains procedure label without P' selector Date: Mon, 03 Mar 2008 16:34:00 -0000 [thread overview] Message-ID: <20080303163349.28572.qmail@sourceware.org> (raw) In-Reply-To: <bug-35222-276@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from dave at hiauly1 dot hia dot nrc dot ca 2008-03-03 16:33 ------- Subject: Re: [4.3/4.4 Regression] EH output contains procedure label without P' selector The same fail occurs on hpux11 if I disable the use of secondary definition symbols for one-only support. Have tested all the alternatives that I can think of for the EH encoding (pc-relative, indirect through function descriptor, etc) and they all lead to linker warnings and segmentation faults linking shared libraries. So, I believe that the only viable work around is to force the use of sjlj exceptions. I'm testing a patch to configure.ac to do this and will submit as soon as I know that libstdc++ links successfully.. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35222
next prev parent reply other threads:[~2008-03-03 16:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-16 22:46 [Bug target/35222] New: [4.3 " danglin at gcc dot gnu dot org 2008-02-16 23:37 ` [Bug target/35222] " danglin at gcc dot gnu dot org 2008-02-17 1:02 ` pinskia at gcc dot gnu dot org 2008-02-17 3:29 ` dave at hiauly1 dot hia dot nrc dot ca 2008-02-17 15:59 ` rguenth at gcc dot gnu dot org 2008-02-17 16:45 ` dave at hiauly1 dot hia dot nrc dot ca 2008-03-03 16:22 ` [Bug target/35222] [4.3/4.4 " rguenth at gcc dot gnu dot org 2008-03-03 16:34 ` dave at hiauly1 dot hia dot nrc dot ca [this message] 2008-03-04 23:32 ` danglin at gcc dot gnu dot org 2008-03-04 23:40 ` danglin at gcc dot gnu dot org 2008-03-05 1:12 ` danglin at gcc dot gnu dot org 2008-03-12 0:58 ` danglin 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=20080303163349.28572.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).