On 09/30/2013 12:03 PM, Geert Uytterhoeven wrote:
On Mon, Sep 30, 2013 at 7:45 PM, David Daney <ddaney.cavm@xxxxxxxxx> wrote:
What about using __builtin_unreachable when we can but turn off warnings
and use do{}while(0) when __builtin_unreachable does not exist? This seems
the both worlds. Newer compilers produce better code with unreachable
anyways.
Simply not true.
do{}while(0) is a NOP it is no more useful than an ';' statement. It
doesn't serve as a magic uninitialized variable hiding mechanism.
You missed the "turn off warnings" part of the "and".
You are correct, I did miss it.
The real problem here is that the kernel is written to expect that BUG()
never returns. Any implementation that has BUG() return, is almost
certainly *not* what we want.
But wieh people select CONFIG_BUG=n they expect the smallest possible code.
These two criteria are mutually exclusive, so something should change.
It is not just the uninitialized variable warning, there can be others
as well (control reaching the end of a non-void function comes to mind).
So I don't think turning off the warnings is a good solution.
That leaves:
1) Remove CONFIG_BUG and make it unconditionally enabled.
2) Make CONFIG_BUG=n imply "static inline void BUG(void){do{}while(1);}"
which might be bigger than with CONFIG_BUG=y
David Daney
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
