GNU bug report logs - #78903
[PATCH] ISO C99 does not support _Noreturn

Previous Next

Full log

Message #14 received at 78903 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Helmut Eller <eller.helmut <at> gmail.com>
Cc: 78903 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu
Subject: Re: bug#78903: [PATCH] ISO C99 does not support _Noreturn
Date: Thu, 26 Jun 2025 11:23:10 +0300

> From: Helmut Eller <eller.helmut <at> gmail.com>
> Cc: Paul Eggert <eggert <at> cs.ucla.edu>,  78903 <at> debbugs.gnu.org
> Date: Thu, 26 Jun 2025 10:08:54 +0200
> 
> On Thu, Jun 26 2025, Eli Zaretskii wrote:
> 
> >> From: Helmut Eller <eller.helmut <at> gmail.com>
> >> Date: Thu, 26 Jun 2025 09:20:51 +0200
> >> 
> >> When I use gcc 14 with -std=gnu99 -Wpedantic I get lots of warnings of
> >> the form
> >> 
> >>  warning: ISO C99 does not support ‘_Noreturn’ [-Wpedantic].
> >
> > Why did you use -Wpedantic?
> 
> To get warnings when I use a non-C99 feature.  Emacs' C code should be
> written in C99.  It would be easier to follow that rule it were checked
> automatically.

AFAIK, Emacs is written in C99 with extensions.

Can you tell why the definition of _Noreturn in src/config.in doesn't
work for you?  AFAIU, it exactly defines _Noreturn to use
__attribute__ ((__noreturn__)), but I'm probably missing something.
is the problem that you use clang, and config.in currently doesn't
cater to that?  If so, the change should be in config.in, I think.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.