On Tuesday 2009-12-22 20:11, David Miller wrote: > >> As far as I can tell, sparcv9v packages are not created in an >> sparcv9-incompatible way. >> >> $ grep -r niagara /usr/lib/rpm >> /usr/lib/rpm/rpmrc:optflags: sparcv9v -O2 -g -m32 -mtune=niagara >> /usr/lib/rpm/rpmrc:optflags: sparc64v -O2 -g -m64 -mtune=niagara >> >> It only uses -mtune, not -mcpu. Or did I err somewhere in this regard? > >-mcpu with sparc64 chip names would turn on 64-bit code generation. But there is no -mcpu here. Just -mtune. Hence it should be producing V7/V8/V8+-compatible code, with niagara-chosen instruction scheduling/etc. >Or at least, it did at one point. You are probably thinking of GCC's ./configure which, when called with --with-cpu=ultrasparc will result in a gcc producing ELF64 objects by default, while --with-cpu=v8 will lead to ELF32 output. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
