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

Hi Tom,

On Tue, Jan 24, 2023 at 08:25:13AM -0700, Tom Tromey wrote:
> 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.

memmove also doesn't work since although this would resolve the
overlapping confusion, gcc still believes specified bound
18446744073709551612 exceeds maximum object size 9223372036854775807.

But it looks like the std::copy approach does just compile without
issue. I'll sent a v3.



      reply	other threads:[~2023-01-24 19:26 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
2023-01-24 19:26   ` 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).