Hi! On Fri, Sep 09, 2022 at 11:07:04AM -0700, Josh Poimboeuf wrote: > 2) Noreturn functions: > > There's no reliable way to determine which functions are designated > by the compiler to be noreturn (either explictly via function > attribute, or implicitly via a static function which is a wrapper > around a noreturn function.) Or just a function that does not return for any other reason. The compiler makes no difference between functions that have the attribute and functions that do not. There are good reasons to not have the attribute on functions that do in fact not return. The not-returningness of the function may be just an implementation accident, something you do not want part of the API, so it *should* not have that attribute; or you may want the callers to a function to not be optimised according to this knowledge (you cannot *prevent* that, the compiler can figure it out it other ways, but still) for any other reason. > This information is needed because the > code after the call to such a function is optimized out as > unreachable and objtool has no way of knowing that. Since June we (GCC) have -funreachable-traps. This creates a trap insn wherever control flow would otherwise go into limbo. Segher
