svn commit: r287217 - head/usr.sbin/syslogd

[Ed Schouten]

2015-08-28 16:38 GMT+02:00 Joerg Sonnenberger <joerg at britannica.bec.de>:
> But the compiler can't tell if it is the *intention* that the function
> never returns. The warning behavior exists because that can easily
> change with macros etc.

I think it's important to keep in mind what this keyword was designed for.

The idea behind this attribute (and the C11 _Noreturn keyword) is to
allow for propagation of optimisation state across compilation units.
You use it to annotate functions in header files, so that the compiler
does not need to handle function return at the call site. This
knowledge can be automatically be inferred if the function is static.

Whether the compiler can throw additional warnings or not based on
whether this keyword is present or what the intent of the programmer
is, is completely irrelevant.

I agree with Bruce that this change makes little sense. I would even
go as far as to say that GCC/Clang should just throw warnings if
_Noreturn is used on a function that is static or used on a definition
instead of a declaration.

-- 
Ed Schouten <ed at nuxi.nl>
Nuxi, 's-Hertogenbosch, the Netherlands
KvK-nr.: 62051717