public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/29487] Shared libstdc++ fails to link Date: Sat, 03 Feb 2007 01:54:00 -0000 [thread overview] Message-ID: <20070203015421.10241.qmail@sourceware.org> (raw) In-Reply-To: <bug-29487-276@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from danglin at gcc dot gnu dot org 2007-02-03 01:54 ------- The patch mentioned in comment #3 was applied to the 4.1 branch and introduces a regression in 4.1.2 on hppa1.1-hp-hpux10.20. As a result, it's no longer possible to use EH exception support on this target. This is the default. Unfortunately, I haven't had a chance to change config.gcc to disable use of EH exceptions or to document this problem. The change installed to fix PR rtl-optimization/29323 causes EH data to emitted for all functions which don't bind locally. This exposed a latent bug in the HP linker; it can't handle the relocations relating to COMDAT sections that have been nullified. On the one hand, this is likely to cause problems for weak (COMDAT) functions which can throw. On the other hand, there aren't any in libstdc++ and the problem didn't expose itself in building at least one large C++ application (lyx). Personally, I believe that the fix for PR 29323 was wrong and has bloated the EH data emitted by GCC. The EH data for a module are only relevant to the functions in the module itself. If a function in a module can't throw, then we don't need EH exception data for it. I think we need to decide how TREE_NOTHROW is to be used. If it's to be used to control the emission of EH data, then it should be set based on analysis of the module being compiled and not whether a function binds locally or not. -- danglin at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mark at codesourcery dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29487
next prev parent reply other threads:[~2007-02-03 1:54 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-16 22:43 [Bug target/29487] New: " danglin at gcc dot gnu dot org 2006-10-16 23:11 ` [Bug target/29487] " danglin at gcc dot gnu dot org 2006-10-19 1:04 ` danglin at gcc dot gnu dot org 2006-11-13 2:25 ` danglin at gcc dot gnu dot org 2006-11-13 2:37 ` pinskia at gcc dot gnu dot org 2006-11-13 3:09 ` dave at hiauly1 dot hia dot nrc dot ca 2006-11-19 21:55 ` dave at hiauly1 dot hia dot nrc dot ca 2006-12-04 1:29 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-03 1:54 ` danglin at gcc dot gnu dot org [this message] 2007-02-03 2:08 ` pinskia at gcc dot gnu dot org 2007-02-03 2:47 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-03 2:50 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-04 22:53 ` mark at codesourcery dot com 2007-02-05 0:15 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-05 3:06 ` mark at codesourcery dot com 2007-02-05 4:02 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-05 5:40 ` mark at codesourcery dot com 2007-02-05 9:06 ` rguenth at gcc dot gnu dot org 2007-02-05 9:07 ` rguenth at gcc dot gnu dot org 2007-02-05 9:22 ` bonzini at gnu dot org 2007-02-05 18:34 ` amylaar at gcc dot gnu dot org 2007-02-05 19:26 ` amylaar at gcc dot gnu dot org 2007-02-05 19:33 ` mark at codesourcery dot com 2007-02-05 19:36 ` amylaar at gcc dot gnu dot org 2007-02-05 19:52 ` amylaar at gcc dot gnu dot org 2007-02-05 20:08 ` mark at codesourcery dot com 2007-02-06 8:27 ` paolo dot bonzini at lu dot unisi dot ch 2007-02-06 8:37 ` bonzini at gnu dot org 2007-02-06 9:27 ` rguenth at gcc dot gnu dot org 2007-02-06 10:18 ` amylaar at gcc dot gnu dot org 2007-02-06 10:39 ` rguenth at gcc dot gnu dot org 2007-02-06 10:42 ` bonzini at gnu dot org 2007-02-06 11:10 ` amylaar at gcc dot gnu dot org 2007-02-06 11:17 ` amylaar at gcc dot gnu dot org 2007-02-06 14:13 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-06 21:18 ` dave at hiauly1 dot hia dot nrc dot ca 2007-02-09 2:53 ` mmitchel at gcc dot gnu dot org 2007-02-10 1:02 ` mmitchel at gcc dot gnu dot org 2007-02-10 1:13 ` mmitchel at gcc dot gnu dot org 2007-02-11 18:58 ` mmitchel at gcc dot gnu dot org 2007-02-11 19:20 ` mmitchel 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=20070203015421.10241.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).