public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/63781] potential linkage issue with libitm.1.dylib Date: Sat, 08 Nov 2014 18:24:00 -0000 [thread overview] Message-ID: <bug-63781-4-lMdrKSdNKo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63781-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63781 --- Comment #5 from howarth at bromo dot med.uc.edu --- The problematic code in eh_cpp.cc appears to be... #if !defined (HAVE_ELF_STYLE_WEAKREF) void *__cxa_allocate_exception (size_t) { return NULL; } void __cxa_throw (void *, void *, void *) { return; } void *__cxa_begin_catch (void *) { return NULL; } void __cxa_end_catch (void) { return; } void __cxa_tm_cleanup (void *, void *, unsigned int) { return; } void _Unwind_DeleteException (_Unwind_Exception *) { return; } #endif /* HAVE_ELF_STYLE_WEAKREF */ } If I append void __cxa_tm_cleanup (void *, void *, unsigned int) { return; } after that the linkage succeeds using the xg++ compiler without unresolved symbols
next prev parent reply other threads:[~2014-11-08 18:24 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-08 17:33 [Bug libitm/63781] New: " howarth at bromo dot med.uc.edu 2014-11-08 17:39 ` [Bug libitm/63781] " howarth at bromo dot med.uc.edu 2014-11-08 18:15 ` howarth at bromo dot med.uc.edu 2014-11-08 18:16 ` howarth at bromo dot med.uc.edu 2014-11-08 18:24 ` howarth at bromo dot med.uc.edu [this message] 2014-11-08 18:35 ` howarth at bromo dot med.uc.edu 2014-11-08 19:04 ` howarth at bromo dot med.uc.edu 2014-11-08 20:20 ` fxcoudert at gcc dot gnu.org 2014-11-08 20:25 ` iains at gcc dot gnu.org 2014-11-08 20:29 ` howarth at bromo dot med.uc.edu 2014-11-08 20:33 ` fxcoudert at gcc dot gnu.org 2014-11-08 20:41 ` fxcoudert at gcc dot gnu.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-63781-4-lMdrKSdNKo@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).