[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Making _Noreturn a no-op in < Clang 16?
From: |
Sam James |
Subject: |
Making _Noreturn a no-op in < Clang 16? |
Date: |
Thu, 19 Jan 2023 02:09:12 +0000 |
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
Best,
sam
signature.asc
Description: Message signed with OpenPGP
- Making _Noreturn a no-op in < Clang 16?,
Sam James <=
- Re: Making _Noreturn a no-op in < Clang 16?, Paul Eggert, 2023/01/18
- Re: Making _Noreturn a no-op in < Clang 16?, Sam James, 2023/01/19
- Re: Making _Noreturn a no-op in < Clang 16?, Paul Eggert, 2023/01/19
- Re: Making _Noreturn a no-op in < Clang 16?, Sam James, 2023/01/19
- Re: Making _Noreturn a no-op in < Clang 16?, Paul Eggert, 2023/01/19
- Re: Making _Noreturn a no-op in < Clang 16?, Sam James, 2023/01/19
- Re: Making _Noreturn a no-op in < Clang 16?, Paul Eggert, 2023/01/20
- Re: Making _Noreturn a no-op in < Clang 16?, Bruno Haible, 2023/01/20