public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: rth@cygnus.com
Cc: mark@codesourcery.com, binutils@sourceware.cygnus.com
Subject: Re: DWARF2 vs. 64-bit MIPS
Date: Tue, 06 Jul 1999 18:53:00 -0000	[thread overview]
Message-ID: <19990707015218.28431.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990706184929.C996@cygnus.com>

   Date: Tue, 6 Jul 1999 18:49:29 -0700
   From: Richard Henderson <rth@cygnus.com>

   Jason didn't follow them.  It does bloat the size of the debug info,
   and it does require you write enough code for 4G of debug info.  
   There should be a way to tell the difference (and switch between the
   two, supposing you _do_ write such big programs!), but I don't know
   what off-hand.

I would normally expect to get such information from sh_info, sh_link,
or sh_entsize.

However, I don't know if SGI thought ahead enough to make any of those
values different for the arguably non-standard debugging information
generated by their tools.  It won't do us much good to implement some
way to detect this case if it doesn't work for SGI generated objects.

Of course, we can fall back on simple if fallible heuristics like ``if
the length appears to be zero, we probably have an eight byte
length.''  On a little endian system, check whether the version number
is valid, and, if not, see if we can make it valid by assuming an
eight byte length.

Ian

      reply	other threads:[~1999-07-06 18:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-02 16:11 Mark Mitchell
1999-07-02 16:44 ` Ian Lance Taylor
1999-07-02 18:44   ` Mark Mitchell
1999-07-06 18:49 ` Richard Henderson
1999-07-06 18:53   ` Ian Lance Taylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990707015218.28431.qmail@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=mark@codesourcery.com \
    --cc=rth@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).