From: Joseph Myers <joseph@codesourcery.com>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>, <libstdc++@gcc.gnu.org>
Subject: Re: Test for __cxa_thread_atexit_impl when cross-compiling libstdc++ for GNU targets
Date: Mon, 12 Oct 2015 23:00:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1510122257390.4306@digraph.polyomino.org.uk> (raw)
In-Reply-To: <561BE80D.6070208@redhat.com>
On Mon, 12 Oct 2015, Bernd Schmidt wrote:
> A similar sequence of tests also occurs for *-aix*. I don't suppose the
> function is likely to exist there or on other non-glibc targets?
Given that the case there has "# We don't yet support AIX's TLS ABI." and
GCC_CHECK_TLS commented out, I don't think this function (which is
concerned with support for destructors of C++11 thread_local variables) is
of any current relevance to that case.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2015-10-12 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 23:19 Joseph Myers
2015-10-12 17:04 ` Bernd Schmidt
2015-10-12 23:00 ` Joseph Myers [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=alpine.DEB.2.10.1510122257390.4306@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).