> We get oopses that have a nice symbolic back-trace, and it reports an
> error IN TOTALLY THE WRONG FUNCTION, because gcc "helpfully" inlined
> things to the point that only an expert can realize "oh, the bug was
> actually five hundred lines up, in that other function that was just
> called once, so gcc inlined it even though it is huge".
The problem isn't with GCC, but the backtrace.
Linus should get himself something that can read the kernel Dwarf3
debugging information provided by GCC and correct the quick backtrace
(which is AFAIK based just on framepointers).