Very aggressive and very known.
If we know how GCC is going to behave in a given situation (and have a fairly
good idea of how it's going to behave in the future), we don't have to worry
about theoretical stardards loopholes like it calling BUG(), do we?
Is there something in the current behavior that's causing trouble (in which
case, what exactly is it), or are the gcc guys (who you mentioned earlier*)
warning that the behavior of upcoming versions of gcc is likely to break
known constructs in the current kernel?
Rob
(Has the english language officially held a funeral for the word "whom" yet?)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/