From: Alexandre Oliva <oliva@adacore.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libsupc++: try cxa_thread_atexit_impl at runtime
Date: Wed, 06 Dec 2023 02:18:04 -0300 [thread overview]
Message-ID: <or5y1bsycz.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAGWvnynnp6Z-d4HwMuS9bj2Oph1xD4vSP6irkVNJzjzW9LCOcw@mail.gmail.com> (David Edelsohn's message of "Tue, 5 Dec 2023 18:15:08 -0500")
On Dec 5, 2023, David Edelsohn <dje.gcc@gmail.com> wrote:
> The error is:
> ld: 0711-317 ERROR: Undefined symbol: __cxa_thread_atexit_impl
> from the new, weak reference.
Thanks.
> Also, earlier in atexit_thread.cc, there is another definition protected by
> _GLIBCXX_HAVE___CXA_THREAD_ATEXIT_IMPL
> not utilized by the new reference.
*nod*, the one I recently added covers a different situation, in which
the _impl symbol is not found in libc at build time.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
next prev parent reply other threads:[~2023-12-06 5:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 1:55 Alexandre Oliva
2023-11-09 8:20 ` Jonathan Wakely
2023-12-01 20:40 ` Alexandre Oliva
2023-12-01 20:41 ` Jason Merrill
2023-12-05 16:10 ` David Edelsohn
2023-12-05 23:15 ` David Edelsohn
2023-12-05 23:19 ` Andrew Pinski
2023-12-06 5:18 ` Alexandre Oliva [this message]
2023-12-06 0:54 ` Alexandre Oliva
2023-12-06 5:28 ` Alexandre Oliva
2023-12-06 12:30 ` Thomas Schwinge
2023-12-06 13:52 ` Jonathan Wakely
2023-12-06 14:40 ` Jonathan Wakely
2023-12-06 22:46 ` Alexandre Oliva
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=or5y1bsycz.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@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).