public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: Replace memcpy with std::copy to avoid some g++ warnings on sparc
Date: Mon, 30 Jan 2023 21:14:58 +0000 (GMT)	[thread overview]
Message-ID: <20230130211458.B6F973858D1E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=214d883794db819617ee60806e3dbeb3d5dab666

commit 214d883794db819617ee60806e3dbeb3d5dab666
Author: Mark Wielaard <mark@klomp.org>
Date:   Sun Jan 15 01:06:16 2023 +0100

    gdb: Replace memcpy with std::copy to avoid some g++ warnings on sparc
    
    For some reason g++ 12.2.1 on sparc produces spurious warnings for
    stringop-overread and restrict in fbsd-tdep.c for a memcpy call.
    Use std::copy to avoid the warnings:
    
    In function ‘void* memcpy(void*, const void*, size_t)’,
        inlined from ‘gdb::optional<std::vector<unsigned char, gdb::default_init_allocator<unsigned char, std::allocator<unsigned char> > > > fbsd_make_note_desc(target_object, uint32_t)’ at ../../binutils-gdb/gdb/fbsd-tdep.c:666:10:
    /usr/include/bits/string_fortified.h:29:33: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int)’ specified bound 18446744073709551612 exceeds maximum object size 9223372036854775807 [-Werror=stringop-overflow=]
    
    In function ‘void* memcpy(void*, const void*, size_t)’,
        inlined from ‘gdb::optional<std::vector<unsigned char, gdb::default_init_allocator<unsigned char, std::allocator<unsigned char> > > > fbsd_make_note_desc(target_object, uint32_t)’ at ../../binutils-gdb/gdb/fbsd-tdep.c:673:10:
    /usr/include/bits/string_fortified.h:29:33: error: ‘void* __builtin_memcpy(void*, const void*, long unsigned int)’ accessing 18446744073709551612 bytes at offsets 0 and 0 overlaps 9223372036854775801 bytes at offset -9223372036854775805 [-Werror=restrict]
    
    gdb/ChangeLog:
    
            * fbsd-tdep.c (fbsd_make_note_desc): Use std::copy instead
            of memcpy.

Diff:
---
 gdb/fbsd-tdep.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/fbsd-tdep.c b/gdb/fbsd-tdep.c
index 203390d9880..3a7cb9b14ea 100644
--- a/gdb/fbsd-tdep.c
+++ b/gdb/fbsd-tdep.c
@@ -663,7 +663,7 @@ fbsd_make_note_desc (enum target_object object, uint32_t structsize)
 
   gdb::byte_vector desc (sizeof (structsize) + buf->size ());
   memcpy (desc.data (), &structsize, sizeof (structsize));
-  memcpy (desc.data () + sizeof (structsize), buf->data (), buf->size ());
+  std::copy (buf->begin (), buf->end (), desc.data () + sizeof (structsize));
   return desc;
 }

                 reply	other threads:[~2023-01-30 21:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230130211458.B6F973858D1E@sourceware.org \
    --to=mark@sourceware.org \
    --cc=gdb-cvs@sourceware.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).