public inbox for cygwin-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: cygwin-cvs@sourceware.org
Subject: [newlib-cygwin] Cygwin: dumper: fix up GCC pragma for g++ 11.2
Date: Thu, 26 Aug 2021 20:22:07 +0000 (GMT)	[thread overview]
Message-ID: <20210826202207.020F8385801E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=3ca80b360c2b294ad781c9c5f76d3b172a61c6dc

commit 3ca80b360c2b294ad781c9c5f76d3b172a61c6dc
Author: Corinna Vinschen <corinna@vinschen.de>
Date:   Thu Aug 26 22:15:49 2021 +0200

    Cygwin: dumper: fix up GCC pragma for g++ 11.2
    
    The GCC diagnostic ignored "-Wstringop-overflow" pragma doesn't work
    as expected anymore.  Use the still working expression.
    
    Signed-off-by: Corinna Vinschen <corinna@vinschen.de>

Diff:
---
 winsup/utils/dumper.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/winsup/utils/dumper.cc b/winsup/utils/dumper.cc
index bc6c68a53..12124e26a 100644
--- a/winsup/utils/dumper.cc
+++ b/winsup/utils/dumper.cc
@@ -557,7 +557,7 @@ dumper::dump_module (asection * to, process_module * module)
   bfd_putl32 (note_length, header.elf_note_header.descsz);
   bfd_putl32 (NT_WIN32PSTATUS, header.elf_note_header.type);
 #pragma GCC diagnostic push
-#pragma GCC diagnostic ignored "-Wstringop-overflow"
+#pragma GCC diagnostic warning "-Wstringop-overflow=1"
 #pragma GCC diagnostic ignored "-Warray-bounds"
   strncpy (header.elf_note_header.name, "win32module", NOTE_NAME_SIZE);
 #pragma GCC diagnostic pop


                 reply	other threads:[~2021-08-26 20:22 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=20210826202207.020F8385801E@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=cygwin-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).