public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Mark Wielaard <mark@klomp.org>, gdb-patches@sourceware.org
Cc: Sam James <sam@gentoo.org>
Subject: Re: [PATCH] gdb: Ignore some stringop-overflow and restrict warnings on sparc
Date: Mon, 23 Jan 2023 11:17:17 -0500	[thread overview]
Message-ID: <ab044390-e565-912b-57e7-22d55b481146@simark.ca> (raw)
In-Reply-To: <20230115005153.872624-1-mark@klomp.org>



On 1/14/23 19:51, Mark Wielaard wrote:
> For some reason g++ 11.2.1 on s390x produces a spurious warning for
> stringop-overread and restruct in fsb-tdep.c for some memcpy calls.

fsb -> fbsd
restruct -> restrict

> Add new DIAGNOSTIC_IGNORE_STRINGOP_OVERFLOW and
> DIAGNOSTIC_IGNORE_RESTRICT macro to suppress these warning.

Can you please put examples of the diagnostics it gets rid of in the
commit message?

Simon

  parent reply	other threads:[~2023-01-23 16:17 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 [this message]
2023-01-24  0:42   ` Mark Wielaard

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=ab044390-e565-912b-57e7-22d55b481146@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.org \
    --cc=sam@gentoo.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).