Re: detect special mips64le dwarf2 line number length encoding

[Daniel Jacobowitz <drow at mvista dot com>]

On Sun, Jan 26, 2003 at 04:24:47AM -0200, Alexandre Oliva wrote:
> On Jan 20, 2003, Daniel Jacobowitz <drow@mvista.com> wrote:
> 
> > On Sun, Jan 19, 2003 at 01:13:58PM -0200, Alexandre Oliva wrote:
> >> On Jan 19, 2003, Daniel Jacobowitz <drow@mvista.com> wrote:
> >> 
> >> > Ask a silly question, but MIPS64 Linux is a brand new userspace port. 
> >> > Why are we using the non-standard DWARF-2 format?  Why not do it the
> >> > normal way?
> >> 
> >> Besides the intent of compatibility with Irix, there are places where
> >> you don't really know whether the object file at hand is for GNU/Linux
> >> or Irix, so using different formats could be, erhm, interesting.  Not
> >> that I've investigated this possibility in much depth, mind you.
> 
> > While I hate to dump more work on you, I would really rather we pursue
> > this than propogate the nonstandard IRIX approach to this.  I really
> > don't think it would be much of a difficulty.
> 
> How 'bout this?  We don't really know whether we're targeting IRIX,
> but TE_TMIPS is not set whenever we are, so this is probably good
> enough.  Ok to install?

[Wow, that's twisted.  It took me a while to figure out how te-tmips.h
gets included.]

I guess I'm okay with this, assuming Eric is.  I think that this leaves
mips64-elf using the nonstandard format, right?  Not a big deal either
way.


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer