public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][_GLIBCXX_INLINE_VERSION] Adapt to_chars/from_chars symbols
Date: Thu, 12 Jan 2023 12:05:01 +0000	[thread overview]
Message-ID: <CACb0b4kRqw06MRX0VMZND1Wu9+dzu8ddrMVzB=A4ad=XPqj0zQ@mail.gmail.com> (raw)
In-Reply-To: <cca7803e-333a-7c99-bfd9-e47471179e7a@gmail.com>

On Mon, 28 Nov 2022 at 20:44, François Dumont wrote:
>
> On 28/11/22 19:35, Jonathan Wakely wrote:
>
>
>
> On Mon, 28 Nov 2022 at 06:07, François Dumont via Libstdc++ <libstdc++@gcc.gnu.org> wrote:
>>
>> This patch is fixing those tests:
>>
>> 20_util/to_chars/float128_c++23.cc
>> std/format/formatter/requirements.cc
>> std/format/functions/format.cc
>> std/format/functions/format_to_n.cc
>> std/format/functions/size.cc
>> std/format/functions/vformat_to.cc
>> std/format/string.cc
>>
>> Note that symbols used in <format> for __ibm128 and __iee128 are untested.
>
>
> We don't need to do this for those symbols, the ALT128 config is incompatible with versioned namespace. If you're using the versioned namespace, you don't need backwards compatibility with the old long double ABI.
>
>
>
>
> Here is the simplified patch then.
>
>     libstdc++: [_GLIBCXX_INLINE_VERSION] Add to_chars/from_chars symbols export
>
>     libstdc++-v3/ChangeLog
>
>             * include/std/format [_GLIBCXX_INLINE_VERSION](to_chars): Adapt __asm symbol
>             specifications.
>             * config/abi/pre/gnu-versioned-namespace.ver: Add to_chars/from_chars symbols
>             export.
>
> Ok to commit ?

I still don't understand why the linker script change is needed, but I
can investigate that myself later.

OK for trunk, thanks.


      reply	other threads:[~2023-01-12 12:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28  6:07 François Dumont
2022-11-28 10:10 ` Jonathan Wakely
2022-11-28 10:21   ` Jonathan Wakely
2022-11-28 18:43     ` François Dumont
2022-11-28 18:45       ` François Dumont
2022-11-28 18:35 ` Jonathan Wakely
2022-11-28 20:44   ` François Dumont
2023-01-12 12:05     ` Jonathan Wakely [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='CACb0b4kRqw06MRX0VMZND1Wu9+dzu8ddrMVzB=A4ad=XPqj0zQ@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).