Comment # 12 on bug 1224402 from Miroslav Beneš

I will not get caught in "broken code, broken tools, broken gcc" discussion but
the thing is that objtool cannot know if it is a bug in the code or not. So it
reports the warning and stops the analysis. Things like this are fixed in the
mainline kernel and const would be appropriate here.

Having said that the support for noreturn functions in objtool is not great.
There have been talks about improving it but it needs to happen in cooperation
with GCC because there is currently no way to know that GCC decided to place
unreachable somewhere (decided that a function is noreturn). I do not know if
there is a progress on this front behind the scenes.