public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/85907] AIX: static libstdc++ and exceptions causes abort Date: Sat, 27 Mar 2021 22:00:04 +0000 [thread overview] Message-ID: <bug-85907-4-UB2yjPRbdk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-85907-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85907 --- Comment #4 from David Edelsohn <dje at gcc dot gnu.org> --- There still are problems because of the manner in which AIX statically links. Normally AIX does not create separate archives of object files for static linking; one statically links by statically linking against the shared object. This combination can create multiple EH tables, which prevents GCC EH from working properly. To link statically, one much ensure that there is only on set of EH tables -- not one in the main application and another one in the statically linked shared library.
prev parent reply other threads:[~2021-03-27 22:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-85907-4@http.gcc.gnu.org/bugzilla/> 2021-03-27 21:10 ` redi at gcc dot gnu.org 2021-03-27 22:00 ` dje at gcc dot gnu.org [this message]
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-85907-4-UB2yjPRbdk@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).