Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: fnf@specifix.com, gdb-patches@sourceware.org
Subject: Re: [RFC] DWARF 2 address size != pointer size
Date: Fri, 12 May 2006 20:07:00 -0000	[thread overview]
Message-ID: <20060512195634.GA16903@nevyn.them.org> (raw)
In-Reply-To: <200605121951.k4CJp1ao000358@elgar.sibelius.xs4all.nl>

On Fri, May 12, 2006 at 09:51:02PM +0200, Mark Kettenis wrote:
> > From: Fred Fish <fnf@specifix.com>
> > Date: Wed, 10 May 2006 14:24:10 -0400
> > 
> > For at least one target, MIPS using the o64 ABI with -mlong64, the
> > target DWARF2 address size used in the DWARF info (32 bit) is not the
> > same as the target pointer size (64 bit).
> 
> Unbelievable.  As if there aren't enough ABI's for MIPS yet.  But how
> can this work?  If the pointers are really 64-bit, how can they be
> encoded in the 32-bit DWARF2 adresses?

[Mark, I just got a delayed bounce from your procmail for an earlier
message.  Let's see if I get another...]

It's a code model thing.  It has 64-bit pointers, but all symbols are
32-bit, and IIRC it actually uses 32-bit ELF.

> I think introducing TARGET_DWARF_ADDR_BIT is a mistake if the debug
> info already encodes the info.

I do too.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-05-12 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 18:24 Fred Fish
2006-05-11 22:44 ` Jim Blandy
2006-05-12 14:21   ` Fred Fish
2006-05-12 18:19     ` Jim Blandy
2006-05-12 19:57 ` Mark Kettenis
2006-05-12 20:07   ` Daniel Jacobowitz [this message]
2006-05-12 22:32     ` David S. Miller
2006-05-12 22:42       ` Daniel Jacobowitz

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=20060512195634.GA16903@nevyn.them.org \
    --to=drow@false.org \
    --cc=fnf@specifix.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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