From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Jonathan Wakely <jwakely@redhat.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [Bug libstdc++/83077] sso-string @ gnu-versioned-namespace.
Date: Fri, 10 Dec 2021 14:58:24 +0100 [thread overview]
Message-ID: <684e64ab-a37a-1548-78b3-25cc7424b2e9@gmail.com> (raw)
In-Reply-To: <CAH6eHdSgK_2vZZwvG67hNcbR1n4u4EFtnyD0sdFjXk1GY5hBWA@mail.gmail.com>
On 09/12/21 11:30 pm, Jonathan Wakely wrote:
> On Thu, 9 Dec 2021 at 21:10, François Dumont via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>> On 08/12/21 5:21 pm, Jonathan Wakely wrote:
>>> 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.
>> I meant to do something similar for the sso string.
> But that's already done by src/c++98/stdexcept.cc
src/c++11/cow-stdexcept.cc (462 lines) has far more code than
src/c++98/stdexcept.cc (93 lines).
I was wondering if I needed to implement something like
_txnal_sso_string_* functions.
Maybe it is the reason I am having the double free errors, will see.
prev parent reply other threads:[~2021-12-10 13:58 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
2021-12-09 21:10 ` François Dumont
2021-12-09 22:30 ` Jonathan Wakely
2021-12-10 13:58 ` François Dumont [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=684e64ab-a37a-1548-78b3-25cc7424b2e9@gmail.com \
--to=frs.dumont@gmail.com \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.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).