Re: [ping] Re: [Patch] arch recognition fix for osabi.c

Daniel Jacobowitz
2003-07-18T14:19:33Z

On Fri, Jul 18, 2003 at 10:13:54AM -0400, Andrew Cagney wrote:
> >Apparently this doesn't work for MIPS, since BFD declares different
> >processors (which it calls "machines") to be incompatible. I'm not
> >quite familiar with MIPS, but I suppose this is not quite true, but
> >that the various MIPS processors cannot be mapped on a one-dimensional
> >quantity that expresses the features of the various CPU's. That could
> >be a valid reason why the MIPS "compatibility function" is written the
> >way it is. Perhaps it can be improved? If so, I think that's the way
> >to go. Otherwise, I think you should register for all CPU types that
> >you support.
>
> Can, to make life less painful, a wild card (-1 safe?) be added?

Now that's a good idea, simple and safe.

I still believe (see my last message in this thread) that the problem
is one in osabi.c; that a return of either of its arguments from the
compatibility function should be accepted. But if a wildcard is
preferred then that would solve the problem too, and I just want the
problem solved...

--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer