From: James E Wilson <wilson@specifixinc.com>
To: Daniel Jacobowitz <drow@false.org>
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: Tue, 09 Nov 2004 00:15:00 -0000 [thread overview]
Message-ID: <1099959313.7589.82.camel@aretha.corp.specifixinc.com> (raw)
In-Reply-To: <20041108234529.GA28651@nevyn.them.org>
On Mon, 2004-11-08 at 15:45, Daniel Jacobowitz wrote:
> Only Irix 5 and Irix 6 use the SGI DWARF format. mips64-linux has been
> using the standard DWARF3 format for a long while.
Ah, you are right. I was misreading the gcc sources I was looking at.
So the mips64-linux port defaults to the standard DWARF3 64-bit dwarf
debug info format, even though there seems to be no reason to use the
64-bit DWARF3 debug format here. If we aren't going to be compatible
with SGI, then we may as well emit 32-bit DWARF3, and only emit 64-bit
DWARF3 if we need it, which will be very unlikely. This is what all
other targets do. The unnecessary use of the 64-bit debug info here is
making debug info, and object files, larger than necessary. Since you
are already using standard DWARF3 here, changing can perhaps be done
without creating a visible ABI change.
It is simpler to leave things the way they already are though, and ask
mips64-openbsd to conform to the mips64-linux choices.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-11-09 0:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 14:28 Mark Kettenis
2004-11-07 15:31 ` Daniel Jacobowitz
2004-11-07 16:29 ` Mark Kettenis
2004-11-07 17:16 ` Daniel Jacobowitz
2004-11-08 20:54 ` James E Wilson
2004-11-08 22:05 ` Mark Kettenis
2004-11-08 23:03 ` James E Wilson
2004-11-08 23:37 ` Thiemo Seufer
2004-11-08 23:50 ` Daniel Berlin
2004-11-08 23:57 ` James E Wilson
2004-11-08 23:46 ` Daniel Jacobowitz
2004-11-09 0:15 ` James E Wilson [this message]
2004-11-09 20:11 ` Dean Luick
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=1099959313.7589.82.camel@aretha.corp.specifixinc.com \
--to=wilson@specifixinc.com \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--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 \
/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).