From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/build] Reimplement Wstringop-overread workaround
Date: Tue, 14 Apr 2026 11:38:10 -0600 [thread overview]
Message-ID: <87o6jlv3wd.fsf@tromey.com> (raw)
In-Reply-To: <20260414134821.2638550-1-tdevries@suse.de> (Tom de Vries's message of "Tue, 14 Apr 2026 15:48:21 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> The gcc PR got closed (because there's no known reproducer with gcc 12 and
Tom> later), but I use the workaround without version limit, because there's no
Tom> actual proof that the problem is fixed.
IIUC from the bug, it is believed to have been fixed though right?
Anyway this seems fine to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2026-04-14 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 13:48 Tom de Vries
2026-04-14 17:38 ` Tom Tromey [this message]
2026-04-16 10:58 ` Tom de Vries
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=87o6jlv3wd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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