Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] [gdb/build] Two Wstringop-overflow updates
Date: Thu, 29 Oct 2026 00:15:30 +0100	[thread overview]
Message-ID: <416f155b-b1d3-4c55-97fd-7e44f0e7351e@suse.de> (raw)
In-Reply-To: <87ecd9pze2.fsf@tromey.com>

On 10/28/26 5:23 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
> 
> Tom> This series contains two patches.
> Tom> The first fixes a Wstringop-overflow false positive.
> 
> What if we just disable this warning?
> It seems like a fairly fragile warning without a big upside.

I'll try to send a patch using that approach tomorrow.

Thanks,
- Tom

      reply	other threads:[~2026-10-28 23:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 12:54 Tom de Vries
2026-10-28 12:54 ` [PATCH 1/2] [gdb/build] Fix Wstringop-overflow in selftests::vex2_to_vex3 Tom de Vries
2026-10-28 12:54 ` [PATCH 2/2] [gdb/build] Add Wno-error=stringop-overflow Tom de Vries
2026-10-28 16:23 ` [PATCH 0/2] [gdb/build] Two Wstringop-overflow updates Tom Tromey
2026-10-28 23:15   ` Tom de Vries [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=416f155b-b1d3-4c55-97fd-7e44f0e7351e@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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