Re: i386 and the COMPAT_50 option

[Martin Husemann <martin%duskware.de@localhost>]

On Fri, Jan 23, 2009 at 06:15:32PM +0000, Christos Zoulas wrote:
>       2. Always compile the hooks in the kernel, not conditionally.
>          + Bloat
>          - Difficult to separate compat and non-compat code.

There is another serious downside for this: for example the %a0 return
values from syscalls on m68k kernels: if you do not avoid the compat code,
you will never notice missing libc stubs for new syscalls. In general
available compat code might hide bugs in new code, so there needs to be
an easy option to build completely-non-compat kernels to run regression
tests.

Martin