From: Jonathan Wakely <jwakely@redhat.com>
To: "François Dumont" <frs.dumont@gmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [Bug libstdc++/83077] sso-string @ gnu-versioned-namespace.
Date: Wed, 8 Dec 2021 16:21:53 +0000 [thread overview]
Message-ID: <CACb0b4kfRq8SA4RotJUOVrRNc-ZqPj+jvkCr+5LDSD-1K6yMeQ@mail.gmail.com> (raw)
In-Reply-To: <958c3e66-1b7c-6932-f5c9-ef8c16366d2a@gmail.com>
It looks like I never replied to this one, sorry.
On Sun, 28 Feb 2021 at 14:51, François Dumont via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Hi
>
> I took in bugzilla and started working on this enhancement.
>
> I am in the step of implementing what is in
> src/c++11/cow-stdexception.cc for the sso string.
Maybe I've misunderstood, but why? The content of that file is
explicitly for the COW string, and only the COW string.
If we make the versioned namespace **only** support SSO strings (and I
think we should do that) then that file won't even be compiled,
because the DUAL_ABI macro will not be defined.
>As I do not know much
> about transactionnal memory yet I prefer to ask confirmation first that
> it is indeed a necessary step to complete PR 83077 ?
It's not essential. If needed, we can disable TM for the versioned namespace.
next prev parent reply other threads:[~2021-12-08 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-83077-19885@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-83077-19885-PbKJj4W9VG@http.gcc.gnu.org/bugzilla/>
2021-02-28 14:51 ` François Dumont
2021-12-08 16:21 ` Jonathan Wakely [this message]
2021-12-09 21:10 ` François Dumont
2021-12-09 22:30 ` Jonathan Wakely
2021-12-10 13:58 ` 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=CACb0b4kfRq8SA4RotJUOVrRNc-ZqPj+jvkCr+5LDSD-1K6yMeQ@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@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).