From: Dean Luick <luick@cray.com>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com,
echristo@redhat.com, seufer@csv.ica.uni-stuttgart.de,
gdb@sources.redhat.com
Subject: Re: Mixing 32-bit and 64-bit DWARF2/3 sections
Date: Tue, 09 Nov 2004 20:58:00 -0000 [thread overview]
Message-ID: <20041109201013.GD10422@saber.us.cray.com> (raw)
In-Reply-To: <200411071428.iA7ES7Fx003013@elgar.sibelius.xs4all.nl>
On Sun, Nov 07, 2004 at 03:28:07PM +0100, Mark Kettenis wrote:
> P.S. It seems that MIPS is the only 64-bit target for which this is a
> problem, since all other 64-bit targets (AMD64, UltraSPARC) still
> use the 32-bit DWARF format.
Not quite. All versions of the Cray X1 compiler will produce 64 bit
DWARF unconditionally. Versions 5.2 and earlier of the Cray X1 compiler
produce the SGI "special" version of 64-bit dwarf. Versions 5.3 and later
follow the DWARF 3 method of differentiating 32- and 64-bit.
Reason for Cray being the same as SGI: Cray was a part of SGI until it was
sold to Terra in 2000.
However, since there currently is no support in binutils/GDB for the Cray X1,
the point is rather moot. :-)
Dean
next prev parent reply other threads:[~2004-11-09 20:11 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
2004-11-09 0:29 ` James E Wilson
2004-11-09 20:58 ` Dean Luick [this message]
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=20041109201013.GD10422@saber.us.cray.com \
--to=luick@cray.com \
--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 \
/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).