From: <gp@qnx.com>
To: <gcc@gcc.gnu.org>
Subject: libsupc++, _cxa references, and Dinkum libcpp
Date: Fri, 16 May 2003 21:24:00 -0000 [thread overview]
Message-ID: <200305162117.RAA25961@hub.ott.qnx.com> (raw)
Hi.
I'm working on porting gcc-3.2.3 to the various QNX platforms. We use both
libstdc++ and Dinkumware libcpp for C++. The difficulty here is that gcc
(actually cc1plus I think) is emitting __cxa* symbols, like the call:
push_throw_library_fn (get_identifier ("__cxa_call_unexpected"), tmp);
in gcc/cp/except.c:init_exception_processing(). So when I build the
Dinkumware with gcc-3.2.3, the libcpp ends up with these undefined references
to various __cxa symbols. These symbols are in libsupc++, but so are a number
of other symbols that conflict with the Dinkumware.
Does a way exist now to resolve this? If not, perhaps the __cxa stuff coud be
split out of libsupc++ into a libcxa.a that gets linked into libsupc++, but
could also be installed/used for this kind of situation. This is what I am
considering doing internally, but I would have to potentially update my lib
with each gcc release.
Thoughts? Comments?
Thanks.
GP
next reply other threads:[~2003-05-16 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 21:24 gp [this message]
2003-05-16 23:55 ` Joe Buck
2003-05-20 16:19 ` gp
2003-05-20 17:34 ` Joe Buck
2003-05-20 18:38 ` gp
2003-05-20 18:38 ` Joe Buck
2003-05-20 19:37 ` gp
2003-05-20 18:41 ` Andrew Pinski
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=200305162117.RAA25961@hub.ott.qnx.com \
--to=gp@qnx.com \
--cc=gcc@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: link
Be 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).