From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed][_GLIBCXX_INLINE_VERSION] Add emul TLS symbol exports
Date: Mon, 30 Oct 2023 13:58:58 +0000 [thread overview]
Message-ID: <CACb0b4k1xvj0FnX4tatcDFJf2Wjv00Yg6hOMG5Ndrgp0GqdNKA@mail.gmail.com> (raw)
In-Reply-To: <08111237-fe7b-4878-9e68-817a602d2996@gmail.com>
On Sun, 29 Oct 2023 at 21:25, François Dumont <frs.dumont@gmail.com> wrote:
>
> libstdc++: [_GLIBCXX_INLINE_VERSION] Add emul TLS symbols
>
> libstdc++-v3/ChangeLog:
>
> * config/abi/pre/gnu-versioned-namespace.ver: Add missing emul TLS
> symbols.
Please put a comment above the two new lines, the same as in gnu.ver:
# targets using emutls
OK with that change, thanks.
next prev parent reply other threads:[~2023-10-30 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 21:24 François Dumont
2023-10-30 13:58 ` Jonathan Wakely [this message]
2023-10-30 18:06 ` François Dumont
2023-10-30 19:13 ` Jonathan Wakely
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=CACb0b4k1xvj0FnX4tatcDFJf2Wjv00Yg6hOMG5Ndrgp0GqdNKA@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.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).