At the moment our problem is that there is some code that has been added to handle the compatability problem caused by u64 objects having different alignment when running on 32-bit and 64-bit systems. This only affects ia64 and x86-64 because all the other 32/64 bit capable systems wisely avoided this issue by making 64-bit objects *always* 8-byte aligned.
It is possible that in the future more such issues will arise (either because we find some more existing interfaces that have this problem, or because new interfaces are introduced that also have this problem). Such new code will also require some compatability functions. These functions will also only be needed on ia64 and x86-64, and even on these systems the code will only be needed if CONFIG_COMPAT=y So I'm failing to see what's wrong with putting such compatabilty code inside a #if defined(CONFIG_COMPAT_FOR_U64_ALIGNMENT) ... #endif to prevent it wasting object code space in kernels that don't need it. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
