GCC 4.3.0 exposes a kernel bug

The main concern is not that someone will *purposefully* write a program that uses this bug to
clobber its own memory, so the fact that someone could have used a non-standard compiler to
achieve this is not relevent.

The real problem is that the new behavior would open up one more way for programmers to
*accidentally* write a program that corrupts its memory, and this could be the memory
corruption bug that adds up with other bugs in the application itself to result in an exploit.