public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Simon Marchi <>
Cc:, Sam James <>
Subject: Re: [PATCH] gdb: Ignore some stringop-overflow and restrict warnings on sparc
Date: Tue, 24 Jan 2023 01:42:45 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Simon,

On Mon, Jan 23, 2023 at 11:17:17AM -0500, Simon Marchi wrote:
> On 1/14/23 19:51, Mark Wielaard wrote:
> > stringop-overread and restruct in fsb-tdep.c for some memcpy calls.
> fsb -> fbsd
> restruct -> restrict

Gah, so many typos, apologies. Fixed.
> > DIAGNOSTIC_IGNORE_RESTRICT macro to suppress these warning.
> Can you please put examples of the diagnostics it gets rid of in the
> commit message?


I'll sent a V2 with the updated commit message.



      reply	other threads:[~2023-01-24  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-15  0:51 Mark Wielaard
2023-01-23 11:45 ` Mark Wielaard
2023-01-23 16:17 ` Simon Marchi
2023-01-24  0:42   ` Mark Wielaard [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).