From: Daniel Jacobowitz <drow@false.org>
To: James E Wilson <wilson@specifixinc.com>
Cc: Mark Kettenis <kettenis@gnu.org>,
echristo@redhat.com, seufer@csv.ica.uni-stuttgart.de,
gdb@sources.redhat.com, gcc@gcc.gnu.org,
binutils@sources.redhat.com
Subject: Re: Mixing 32-bit and 64-bit DWARF2/3 sections
Date: Mon, 08 Nov 2004 23:50:00 -0000 [thread overview]
Message-ID: <20041108234529.GA28651@nevyn.them.org> (raw)
In-Reply-To: <418FDD06.9030404@specifixinc.com>
On Mon, Nov 08, 2004 at 12:54:30PM -0800, James E Wilson wrote:
> Unfortunately, the way that SGI extended DWARF2 caused problems, as it
> resulted in ambiguous DWARF info, so the DWARF3 committee defined a
> different way that is self descriptive. But since this happened after
> Irix6 had already been released, and SGI could not break backwards
> compatibility with Irix6, N64 still uses the non-standard 64-bit DWARF
> format that SGI invented. And gcc uses this non-standard 64-bit DWARF
> format for all mips64 targets, for consistency, and to conform with the ABI.
This is not correct.
% grep DWARF_INITIAL_LENGTH_SIZE *
iris.h:#define DWARF_INITIAL_LENGTH_SIZE DWARF_OFFSET_SIZE
%
Only Irix 5 and Irix 6 use the SGI DWARF format. mips64-linux has been
using the standard DWARF3 format for a long while.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-11-08 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 15:31 Mark Kettenis
2004-11-07 16:29 ` Daniel Jacobowitz
2004-11-07 17:16 ` Mark Kettenis
2004-11-08 0:19 ` Daniel Jacobowitz
2004-11-08 21:44 ` James E Wilson
2004-11-08 23:03 ` Mark Kettenis
2004-11-08 23:37 ` James E Wilson
2004-11-08 23:46 ` Thiemo Seufer
2004-11-08 23:55 ` Daniel Berlin
2004-11-09 0:15 ` James E Wilson
2004-11-08 23:50 ` Daniel Jacobowitz [this message]
2004-11-09 0:29 ` James E Wilson
2004-11-09 20:58 ` Dean Luick
2004-11-09 22:10 David Anderson
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=20041108234529.GA28651@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=seufer@csv.ica.uni-stuttgart.de \
--cc=wilson@specifixinc.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).