Stanislaw Skowronek wrote: > Hello, > > why do we attempt to compile the kernel with 32-bit GAS abi and 64-bit GCC > abi? It optimizes away a few hundred kB of kernel code, but requires in turn a sign-extended load-address plus ugly objcopy hacks. > Is it because the module loader is broken and supports only 32-bit > ELFs? Then what about machines which load their kernels at weird 64-bit > addresses, like 0xa800000020004000 (Octane)? Ah, the same as for IP28. :-) They can't be supported by the current scheme. > I have changed it to 64-bit abi in my Octane kernel, because it won't even > compile otherwise. I've got gcc 3.3.2, gas 2.14. You'll have to extend all the hand-coded asm memory accesses to do 64bit adressing as well. Thiemo
