On Mon, Mar 26, 2007 at 01:09:37PM +0100, Maciej W. Rozycki wrote: > > Hmm, from the back of my head I think it should not be a problem -- IIRC > the versions of GCC that did not support explicit relocs for 64-bit ELF > would force "-mno-explicit-relocs" internally even if asked otherwise. > They did not support "-msym32" either, which went in later, and then > non-PIC support for 64-bit explicit relocs went in earlier than for PIC -- > quite unsurprisingly, as %higher() and %highest() are not necessarily > rocket science unlike %disp() and friends. > > If anybody cares I could probably make the excavations needed to verify > the above. That would be appreciated. I did that on my side, I also tried to build a few 64-bit test kernels with gcc 3.3 and 4.1.2 yesterday and did not find any real reason why we would still need -mno-explicit-relocs. Thiemo said there was something like a modern gcc in combination with old binutils. That's the comination I haven't tested. Ralf
