public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-3607] libstdc++: Ignore -Wignored-qualifiers warning in <variant>
Date: Wed,  2 Nov 2022 12:56:14 +0000 (GMT)	[thread overview]
Message-ID: <20221102125616.845CD3858C66@sourceware.org> (raw)

https://gcc.gnu.org/g:cf35818a390e7cb4b1a4fa70c243ede59d6cbbac

commit r13-3607-gcf35818a390e7cb4b1a4fa70c243ede59d6cbbac
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Nov 1 11:17:35 2022 +0000

    libstdc++: Ignore -Wignored-qualifiers warning in <variant>
    
    The warning is wrong here, the qualifier serves a purpose and is not
    ignored (c.f. PR c++/107492).
    
    libstdc++-v3/ChangeLog:
    
            * include/std/variant (__variant::_Multi_array::__untag_result):
            Use pragma to suppress warning.

Diff:
---
 libstdc++-v3/include/std/variant | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/libstdc++-v3/include/std/variant b/libstdc++-v3/include/std/variant
index c234b54421e..ba8492b6985 100644
--- a/libstdc++-v3/include/std/variant
+++ b/libstdc++-v3/include/std/variant
@@ -831,10 +831,13 @@ namespace __variant
 	: false_type
 	{ using element_type = _Tp; };
 
+#pragma GCC diagnostic push
+#pragma GCC diagnostic ignored "-Wignored-qualifiers"
       template <typename... _Args>
 	struct __untag_result<const void(*)(_Args...)>
 	: false_type
 	{ using element_type = void(*)(_Args...); };
+#pragma GCC diagnostic pop
 
       template <typename... _Args>
 	struct __untag_result<__variant_cookie(*)(_Args...)>

                 reply	other threads:[~2022-11-02 12:56 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=20221102125616.845CD3858C66@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.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).