| On 11 Mar 2003, Linus Torvalds wrote:
| > If there is a well-known list of compilers, we should put a BIG warning
| > in some core kernel file to guide people to upgrade (or maybe work
| Not enough, nobody would notice and today most end user doesn't
| compile the kernel himself, they are just shipped by a broken kernels.
| We *also* need a mechanism to know the kernel was compiled with a
| broken compiler (from kernel point of view of course, not the latest
| C++ features). Like the 'tainted' approach but this would be marked as
| broken/miscompiled/etc. To be able to tell the user *immediately* to
| complain to his vendor instead hunting/finding the bug again and
| again, as happening now.
Not quite what you describe, but the in-kernel-config (ikconfig) patch by
me & some HP folks saves a "built-with" string along with the .config file
(as a CONFIG option, of course).
| BTW, if possible having the Code both before and after when a fault
| happens could also help a lot in the future.
Do you just mean more opcode decoding?
| And in general, an oops counter would be also useful, not spending too
| much time decoding potentialy bogus oopses.
-- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/