Thanks for the quick reply :)
> > Either way why is this so? AFAIK gcc 3.2 has abi incompatiblities
> > w.r.t. C++ and not C (which the kernel+modules are written in).
>
> there are some cornercase C ABI changes but nobody except DAC960 will
> ever hit those.
what are these? i am just curious about the change as i dont
see them (probably did not search hard) documented/listed on
gcc site. C++ ABI changes have some mention on some sites, but
NOT on C ABI.
> The more serious change is that the kernel contains
> workarounds for older compilers (the test used is major < 3) that
> changes the size of structures etc etc, and that breaks the module
> stuff.
so does this mean that: these workarounds now fixed in gcc 3.X?
and its just that the workaround employed in kernel source (for
gcc 2.X) is different than the way gcc 3.X fixes them and hence
objects generated from gcc 3.X and 2.X (w.r.t kernel sources+modules)
dont mix well?
thanks
A.
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
-
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/