bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: stdalign: Document a clang 17 bug
Date: Mon, 12 Feb 2024 13:19:25 +0100	[thread overview]
Message-ID: <4172721.tdWV9SEqCh@nimes> (raw)

The configure test
  checking for alignas and alignof...
reports 'yes, <stdalign.h> macros' with gcc, but 'no' with
clang 17 and CC="clang -std=gnu2x". In my opinion, this is a clang bug.
This patch documents it.

2024-02-12  Bruno Haible  <bruno@clisp.org>

	stdalign: Document a clang 17 bug.
	* doc/posix-headers/stdalign.texi: Mention a clang 17 bug.

diff --git a/doc/posix-headers/stdalign.texi b/doc/posix-headers/stdalign.texi
index 7f75a15540..4f9c2dd186 100644
--- a/doc/posix-headers/stdalign.texi
+++ b/doc/posix-headers/stdalign.texi
@@ -45,6 +45,10 @@
 @code{alignasof} module, as such code should use @code{alignas} and
 @code{alignof} without checking these two macros.  (Gnulib's
 now-deprecated @code{stdalign} module defines these two macros.)
+@c https://github.com/llvm/llvm-project/issues/81472
+Clang 17 does not support an @code{alignas} attribute in the
+specifier-qualifier position of a member declaration.
 @end itemize
 Portability problems not fixed by Gnulib:

                 reply	other threads:[~2024-02-12 12:19 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:

  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=4172721.tdWV9SEqCh@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \


* 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).