This is the mail archive of the
mailing list for the binutils project.
Re: RFC & patch: Rework MIPS command-line handling
Eric Christopher <email@example.com> writes:
> > > I took my cue from R3000 and R4000, which were the standard before.
> > So, historically, those defines _seem_ to be used less as 'processor'
> > defines and more as 'GPR size' defines, at least looking at the way
> > GCC defined them in say 3.0.x.
> It was annoying too. There _were_ preprocessor directives for mips and
> mips64.. anyhow
Ugh. Ok, I'll keep _R3000 & _R4000 as they are now, and add the
_MIPS_ARCH and _MIPS_TUNE that Chris suggested.
Question: if gcc treats two processors as the same for scheduling,
should they have the same _MIPS_ARCH and _MIPS_TUNE value? Like,
should -march=r2000 and -march=r3000 set _MIPS_ARCH to the same
value (_MIPS_R3000?) to reflect what GCC's doing, or should there
be separate _MIPS_R2000 and _MIPS_R3000 defines? How about
-mtune= and _MIPS_TUNE?