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 r14-3104] libstdc++: Suppress clang -Wc99-extensions warnings in <complex>
Date: Wed,  9 Aug 2023 14:21:42 +0000 (GMT)	[thread overview]
Message-ID: <20230809142142.A67153857B93@sourceware.org> (raw)

https://gcc.gnu.org/g:798b1f04762c84b7cf38c4af5aba1b52823864ba

commit r14-3104-g798b1f04762c84b7cf38c4af5aba1b52823864ba
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Aug 8 22:19:49 2023 +0100

    libstdc++: Suppress clang -Wc99-extensions warnings in <complex>
    
    This prevents Clang from warning about the use of the non-standard
    __complex__ keyword.
    
    libstdc++-v3/ChangeLog:
    
            * include/std/complex: Add diagnostic pragma for clang.

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

diff --git a/libstdc++-v3/include/std/complex b/libstdc++-v3/include/std/complex
index 0ba2167bf022..a4abe9aa96a9 100644
--- a/libstdc++-v3/include/std/complex
+++ b/libstdc++-v3/include/std/complex
@@ -47,6 +47,11 @@
 // Get rid of a macro possibly defined in <complex.h>
 #undef complex
 
+#ifdef __clang__
+#pragma clang diagnostic push
+#pragma clang diagnostic ignored "-Wc99-extensions"
+#endif
+
 #if __cplusplus > 201703L
 # define __cpp_lib_constexpr_complex 201711L
 #endif
@@ -2642,4 +2647,8 @@ _GLIBCXX_END_NAMESPACE_VERSION
 
 #endif  // C++11
 
+#ifdef __clang__
+#pragma clang diagnostic pop
+#endif
+
 #endif  /* _GLIBCXX_COMPLEX */

                 reply	other threads:[~2023-08-09 14:21 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=20230809142142.A67153857B93@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).