mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Cc: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Subject: Re: [musl] Alignment attribute in headers
Date: Sun, 21 Apr 2024 09:38:38 +0200	[thread overview]
Message-ID: <ZiTCflgUNfvtT96w@voyager> (raw)
In-Reply-To: <20240421091605.4b4e7d2e@inria.fr>

Am Sun, Apr 21, 2024 at 09:16:05AM +0200 schrieb Jₑₙₛ Gustedt:
> Since this is unified starting with C23 and I think we morally should
> have C conformance first and fallbacks only if imperatively needed
> I would go for
>

Ugh. Let the bike shedding begin. I will tell you that moral arguments
about software don't make a lot of sense to me, though.

>   #if __STDC_VERSION >= 202311L || __cplusplus >= 201100L
>   /* use alignas */
>   #elif __STDC_VERSION >= 201100L
>   /* use _Alignas */
>   #elif __GNUC__
>   /* use attribute */
>   #endif
>

Did you not read the part about the GCC version that claims C11
conformance but doesn't have _Alignas? Yes, that's a bug. Yes, it was
fixed. No, musl can't break compatibility with it.

If not for that, I would have gone with this version too, but that's
like saying "your code would be perfect if it did work".

Ciao,
Markus


  reply	other threads:[~2024-04-21  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21  3:51 Michael Forney
2024-04-21  4:54 ` Markus Wichmann
2024-04-21  7:16   ` Jₑₙₛ Gustedt
2024-04-21  7:38     ` Markus Wichmann [this message]
2024-04-21 10:23       ` Jₑₙₛ Gustedt
2024-04-21 10:31         ` Sam James
2024-04-21 17:40         ` Markus Wichmann
2024-04-21 15:50 ` Thorsten Glaser
2024-04-21 16:44   ` Alexander Monakov
2024-04-21 17:20   ` Markus Wichmann
2024-04-21 18:23     ` Thorsten Glaser
2024-04-21 19:04     ` Michael Forney
2024-04-21 23:48 ` Rich Felker
2024-04-24  0:45   ` Michael Forney
2024-04-24  2:54     ` Markus Wichmann
2024-04-24  7:39     ` Jon Chesterfield
2024-04-24  7:55       ` Jeffrey Walton
2024-04-24  9:49         ` Jon Chesterfield

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=ZiTCflgUNfvtT96w@voyager \
    --to=nullplan@gmx.net \
    --cc=jens.gustedt@inria.fr \
    --cc=musl@lists.openwall.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).