This is the mail archive of the 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: The new mips gas breaks gcc 2.96

On Mon, Aug 05, 2002 at 10:51:53AM +0200, Maciej W. Rozycki wrote:
> On Fri, 2 Aug 2002, H. J. Lu wrote:
> > >  How about adding a translation from "-mcpu=x" to "-march=x -mtune=x" to
> > > your gcc's specs?  It should be the least maintenance trouble and is
> > > probably the right solution for an obsolete compiler. 
> > 
> > I can't force it for all the users of my Linux binutils. Besides, until
> > gcc 3.2 is stable enough, I won't obsolete my gcc 2.96.
>  You may state an appropriate version of your gcc 2.96 is needed for MIPS

Although I still use gcc 2.96, I have no plan to touch it unless it is
absolutely necessary. Besides, I can't force it.

> starting from version x of your binutils.  You may even check it at the
> configure time.  It's a reasonable assumption -- you don't force all the
> users of your binutils to upgrade them, either, so they may either stick

I'd like to get my binutils tested as much as posible. The last thing
I want is to hear that the new binutils generates bad binaries 2 years
from now just because he/she couldn't use the new binutils earlier due
to the gcc version issue.

> to versions they have now or upgrade both packages at the same time.
> AFAIK, up to 3.x gcc didn't support MIPS/Linux out of the box anyway, so
> patches for it are needed anyway. 
>  Anyway, do as you want to, as long as nobody complains here of binutils
> as distributed by FSF not working with gcc 2.96... 

I guess they won't complain it to me :-).


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