From: Sam James <sam@gentoo.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Ben Sherman <ben.sherman@chicagotrading.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: avoid uninitialized read in basic_string constructor
Date: Fri, 03 Nov 2023 13:53:07 +0000 [thread overview]
Message-ID: <87y1ffq6xp.fsf@gentoo.org> (raw)
In-Reply-To: <CACb0b4k_4==WjQDOmZDLvLSnnd2ovpCkmP2dkYw=nQ+Qy3GKcg@mail.gmail.com>
Jonathan Wakely <jwakely@redhat.com> writes:
> On Thu, 2 Nov 2023 at 19:58, Ben Sherman <ben.sherman@chicagotrading.com> wrote:
>>
>> Tested on x86_64-pc-linux-gnu, please let me know if there's anything
>> else needed. I haven't contributed before and don't have write access, so
>> apologies if I've missed anything.
>
> This was https://gcc.gnu.org/PR109703 (and several duplicates) and
> should already be fixed in all affected branches. Where are you seeing
> this?
It would help to know where they got their GCC from too. Ben?
prev parent reply other threads:[~2023-11-03 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 19:56 Ben Sherman
2023-11-02 20:53 ` Jonathan Wakely
2023-11-03 13:51 ` Ben Sherman
2023-11-03 14:27 ` Jonathan Wakely
2023-11-03 13:53 ` Sam James [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=87y1ffq6xp.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=ben.sherman@chicagotrading.com \
--cc=gcc-patches@gcc.gnu.org \
--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).