public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Mark Wielaard <>
Cc:,  Simon Marchi <>,
	 Sam James <>
Subject: Re: [PATCHv2] gdb: Ignore some stringop-overflow and restrict warnings on sparc
Date: Tue, 24 Jan 2023 08:25:13 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Mark Wielaard's message of "Tue, 24 Jan 2023 01:44:44 +0100")

>>>>> "Mark" == Mark Wielaard <> writes:

Mark> For some reason g++ 12.2.1 on sparc produces a spurious warning for
Mark> stringop-overread and restrict in fbsd-tdep.c for some memcpy calls.
Mark> DIAGNOSTIC_IGNORE_RESTRICT macro to suppress these warnings:

Mark>    gdb::byte_vector desc (sizeof (structsize) + buf->size ());
Mark>    memcpy ( (), &structsize, sizeof (structsize));
Mark> +#if defined (__sparc__)
Mark> +  /* g++ 12.2.1 on sparc seems confused about the vector buf sizes.  */
Mark> +#endif
Mark>    memcpy ( () + sizeof (structsize), buf->data (), buf->size ());
Mark> +#if defined (__sparc__)
Mark> +#endif

Is there any chance that std::copy or std::memmove would avoid the
warning?  It would be nice if this could be fixed without having to add
a bunch of #if goo.

However, if not, this is ok.


  parent reply	other threads:[~2023-01-24 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24  0:44 Mark Wielaard
2023-01-24  3:32 ` Enze Li
2023-01-24  9:35   ` Mark Wielaard
2023-01-24 15:25     ` Tom Tromey
2023-01-24 15:19   ` Tom Tromey
2023-01-24 15:22     ` Tom Tromey
2023-01-24 15:25 ` Tom Tromey [this message]
2023-01-24 19:26   ` 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:

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