On Thu, 27 Feb 2003 13:05:02 +0100 (MET)
"Maciej W. Rozycki" <firstname.lastname@example.org> wrote:
> On Thu, 27 Feb 2003, Yoichi Yuasa wrote:
> > $ mipsel-linux-gcc -v -mcpu=vr4100 -mips2 -Wa,--trap -xassembler -c
> > /dev/null -o /dev/null
> > Reading specs from /usr/local/lib/gcc-lib/mipsel-linux/2.95.4/specs
> > gcc version 2.95.4 20011002 (Debian prerelease)
> > /usr/local/mipsel-linux/bin/as -EL -mips2 -mcpu=vr4100 -v -KPIC --trap -o
> > /dev/null /dev/null
> > GNU assembler version 188.8.131.52.1 (mipsel-linux) using BFD version
> > 184.108.40.206.1 20020307 Debian/GNU Linux
> Ah, I see how it happens now -- "-mipsN" has a higher priority than
> "-mcpu=" (but lower than "-march=") so in this case "-mips2" overrides
> "-mcpu=vr4100". How about:
> GCCFLAGS += -mcpu=vr4100 -Wa,--trap
That is fine.
However, the following warning is displayed.
Warning: The -mcpu option is deprecated. Please use -march and -mtune instead.
> Ralf, it seems the "-mcpu=XXXX -mipsN" settings are contradicting and
> XXXX is ignored (I don't see it as my gcc translates "-mcpu=XXXX" into
> "-march=XXXX -mtune=XXXX" as a step towards transiting to 3.x). I think
> the following settings would be more reasonable:
> GCCFLAGS += -mabi=32 -mcpu=XXXX # for the 32-bit kernel
> GCCFLAGS += -mabi=n64 -mcpu=XXXX # for the 64-bit kernel
> (additional processor-specific flags skipped). Is that supported by the
> oldest version of binutils you want to support?