From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
"libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] sso-string@gnu-versioned-namespace [PR83077]
Date: Thu, 17 Aug 2023 18:22:06 +0100 [thread overview]
Message-ID: <CACb0b4nmVG9xFSAnueH+BK7P8Ug3vu-0h0oy1npOQ5sjifockw@mail.gmail.com> (raw)
In-Reply-To: <91dc6383-6bff-ce6c-b24d-81cd2ab2dce8@gmail.com>
On Sun, 13 Aug 2023 at 14:27, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Here is the fixed patch tested in all 3 modes:
>
> - _GLIBCXX_USE_DUAL_ABI
>
> - !_GLIBCXX_USE_DUAL_ABI && !_GLIBCXX_USE_CXX11_ABI
>
> - !_GLIBCXX_USE_DUAL_ABI && _GLIBCXX_USE_CXX11_ABI
>
> I don't know what you have in mind for the change below but I wanted to
> let you know that I tried to put COW std::basic_string into a nested
> __cow namespace when _GLIBCXX_USE_CXX11_ABI. But it had more impact on
> string-inst.cc so I preferred the macro substitution approach.
I was thinking of implementing the necessary special members functions
of __cow_string directly, so they are ABI compatible with the COW
std::basic_string but don't actually reuse the code. That would mean
we don't need to compile and instantiate the whole COW string just to
use a few members from it. But that can be done later, the macro
approach seems OK for now.
>
> There are some test failing when !_GLIBCXX_USE_CXX11_ABI that are
> unrelated with my changes. I'll propose fixes in coming days.
Which tests? I run the entire testsuite with
-D_GLIBCXX_USE_CXX11_ABI=0 several times per day and I'm not seeing
failures.
I'll review the patch ASAP, thanks for working on it.
next prev parent reply other threads:[~2023-08-17 17:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 5:13 François Dumont
2023-08-11 5:43 ` François Dumont
2023-08-11 7:51 ` Jonathan Wakely
2023-08-13 13:27 ` François Dumont
2023-08-13 19:51 ` François Dumont
2023-08-17 17:17 ` François Dumont
2023-08-24 17:33 ` François Dumont
2023-08-17 17:22 ` Jonathan Wakely [this message]
2023-08-17 17:40 ` François Dumont
2023-08-17 18:59 ` Jonathan Wakely
2023-08-17 19:37 ` Jonathan Wakely
2023-08-17 19:44 ` Jonathan Wakely
2023-08-17 23:31 ` Jonathan Wakely
2023-08-19 19:44 ` François Dumont
2023-10-07 12:25 ` François Dumont
2023-10-07 19:32 ` François Dumont
2023-10-09 14:42 ` Iain Sandoe
2023-10-09 16:27 ` Iain Sandoe
2023-10-09 17:38 ` François Dumont
2023-10-24 4:55 ` François Dumont
2024-02-28 18:37 ` François Dumont
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=CACb0b4nmVG9xFSAnueH+BK7P8Ug3vu-0h0oy1npOQ5sjifockw@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--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).