bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Gnulib bugs <bug-gnulib@gnu.org>
Cc: "Arsen Arsenović" <arsen@aarsen.me>
Subject: Making _Noreturn a no-op in < Clang 16?
Date: Thu, 19 Jan 2023 02:09:12 +0000	[thread overview]
Message-ID: <F3CDF510-E88C-4BDC-99E9-E10004E6ADF3@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

Hi all,

Over on bug-gawk, we ended up finding that Clang was miscompiling certain
expressions involving _Noreturn. This is fixed in Clang's git repo but not
in any released version. It should be in 16.0.

Paul suggested [0] that gnulib ought to #define _Noreturn to blank
for known-broken Clang versions, especially given finding such
broken patterns isn't easy.

This seems like a reasonable path forward. I'm concerned about
gnulib versions in various released bits of GNU software (diffutils
just got a release, for example) without this workaround in.

What do you think?

[0] https://lists.gnu.org/archive/html/bug-gawk/2023-01/msg00004.html


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

             reply	other threads:[~2023-01-19  2:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  2:09 Sam James [this message]
2023-01-19  4:17 ` Making _Noreturn a no-op in < Clang 16? Paul Eggert
2023-01-19 20:44   ` Sam James
2023-01-19 21:20     ` Paul Eggert
2023-01-19 21:30       ` Sam James
2023-01-20  3:40         ` Paul Eggert
2023-01-20  4:20           ` Sam James
2023-01-20  9:16             ` Paul Eggert
2023-01-20 10:25               ` Bruno Haible

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=F3CDF510-E88C-4BDC-99E9-E10004E6ADF3@gentoo.org \
    --to=sam@gentoo.org \
    --cc=arsen@aarsen.me \
    --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).