This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: RFC: Mips option parsing patch

From: Eric Christopher <echristo at redhat dot com>
To: Richard Sandiford <rsandifo at redhat dot com>
Cc: Daniel Jacobowitz <drow at mvista dot com>, binutils at sources dot redhat dot com
Date: 27 Nov 2001 13:51:31 -0800
Subject: Re: RFC: Mips option parsing patch
References: <20011126145844.A5690@nevyn.them.org><1006819122.1466.4.camel@ghostwheel.cygnus.com><20011127112844.A3734@nevyn.them.org> <wvn7kscvtjl.fsf@talisman.cambridge.redhat.com>


> 
> Is this patch for mainline or the upcoming release branch?  Any chance
> it could just be the branch, if that wasn't the idea all along?  I can
> see the need for the next release to be compatible with gcc 3.0, but
> I'm not sure why CVS mainline has to be, especially since CVS gcc
> ought to work with the new scheme.

If it's a workaround it should be branch only. I was considering the
possibility of making mips1/2 set gp32 and mips3/4 set gp64 (unless
otherwise overridden).

This still screams of a hack to me, but will give the most backwards
compatibility for people doing things like:

-march=foo -mipsX

-eric

-- 
Fridays are not "pants optional"

References:
- RFC: Mips option parsing patch
  - From: Daniel Jacobowitz
- Re: RFC: Mips option parsing patch
  - From: Eric Christopher
- Re: RFC: Mips option parsing patch
  - From: Daniel Jacobowitz
- Re: RFC: Mips option parsing patch
  - From: Richard Sandiford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]