From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH] intprops: document fix for GCC bug 68193
Date: Tue, 30 Apr 2024 19:37:42 -0700 [thread overview]
Message-ID: <20240501023747.9220-1-eggert@cs.ucla.edu> (raw)
* lib/intprops-internal.h (_GL__GENERIC_BOGUS):
GCC bug 68193 is fixed in GCC 14. This is just for documentation,
as _GL__GENERIC_BOGUS is not consulted in GCC 14.
---
ChangeLog | 7 +++++++
lib/intprops-internal.h | 4 ++--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index bf68bf6369..e2c736f854 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2024-04-30 Paul Eggert <eggert@cs.ucla.edu>
+
+ intprops: document fix for GCC bug 68193
+ * lib/intprops-internal.h (_GL__GENERIC_BOGUS):
+ GCC bug 68193 is fixed in GCC 14. This is just for documentation,
+ as _GL__GENERIC_BOGUS is not consulted in GCC 14.
+
2024-04-30 Bruno Haible <bruno@clisp.org>
*printf: Don't invoke gl_PRINTF_DIRECTIVE_N when it's not needed.
diff --git a/lib/intprops-internal.h b/lib/intprops-internal.h
index b5ba8d7cbd..443024c665 100644
--- a/lib/intprops-internal.h
+++ b/lib/intprops-internal.h
@@ -185,10 +185,10 @@
/* Nonzero if this compiler has GCC bug 68193 or Clang bug 25390. See:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68193
https://llvm.org/bugs/show_bug.cgi?id=25390
- For now, assume all versions of GCC-like compilers generate bogus
+ For now, assume GCC < 14 and all Clang versions generate bogus
warnings for _Generic. This matters only for compilers that
lack relevant builtins. */
-#if __GNUC__ || defined __clang__
+#if (__GNUC__ && __GNUC__ < 14) || defined __clang__
# define _GL__GENERIC_BOGUS 1
#else
# define _GL__GENERIC_BOGUS 0
--
2.44.0
reply other threads:[~2024-05-01 2:38 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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240501023747.9220-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@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).