RFC & patch: Rework MIPS command-line handling

[Mark D. Baushke]

Richard Sandiford <rsandifo@redhat.com> writes:
> 
> > >     For example, if "mips64-elf-gcc -mips1" chooses o32 code
> > >     (as it does now) then "mips64-elf-gcc -march=r3000" should do the same.
> > 
> > This may break the 'No ABI' case which means default ABI plus e.g.
> > -mlong64 as it is used in the embedded world. OTOH, basing this usage
> > on o32/o64 in future is probably a good idea.
> 
> I'm not sure how it could break things like that.  -mlong64 only
> controls type sizes.

In MIPS I the -mlong64 also implies the use of register pairs right? 
Where in MIPS III, the -mlong64 implies the use of a single register.

If 'No ABI' is in use, would you be able to figure out if you are
linking between those two variants of -mlong64 compiled code?

	Curious,
	-- Mark