On Tue, 18 Apr 2000, Robert Dinse wrote:
> info. At any rate, yes, it is documented there but it's inclusion in
> the compilation flags is nonsensical if the documentation is correct.
-fstrict-aliasing (and by extension, -fno-strict-aliasing) was first
introduced in GCC 2.95 (maybe 2.95.1), and defaulted to being always
enabled. It was found that it severely broke the kernel, and it was
changed to be off by default in 2.95.2.
It is in the CFLAGS to make sure it is always disabled, just in case
somebody's building it with 2.95(.1).
What's the problem with it, anyway? It's only specified in one place, and
doesn't hurt anything.
--Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:13 EST