Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: mark.kettenis@xs4all.nl, fnf@specifix.com, gdb-patches@sourceware.org
Subject: Re: [RFC] DWARF 2 address size != pointer size
Date: Fri, 12 May 2006 22:42:00 -0000	[thread overview]
Message-ID: <20060512223213.GA20204@nevyn.them.org> (raw)
In-Reply-To: <20060512.151851.65038908.davem@davemloft.net>

On Fri, May 12, 2006 at 03:18:51PM -0700, David S. Miller wrote:
> I guess this is a side effect of using the MIPS 32-bit ELF target
> rather than something explicit the MIPS backend of GCC is doing
> to tinker with the DWARF output format?

Probably.

> Actually, there is a Sparc situation which is more like this MIPS
> case.  For -mcpu=v8plus{,a,b} and friends, we're generating 32-bit
> code and using 32-bit SPARC ELF, but certain registers are available
> for full 64-bit integer operations (for "long long").  We don't handle
> this in GDB currently because there is no easy way to get at the full
> 64-bit register values in a 32-bit process with a 32-bit gdb.  With a
> 64-bit GDB we can easily do this, and under Linux/Sparc there are
> special versions of the ptrace commands which allow passing 64-bit
> register values back and forth to/from a 32-bit debugger.
> 
> I've always wanted to add support for that, but it's going to be real
> ugly stuff and take us away from the nice unified Sparc ptrace()
> support which several Sparc targets are sharing right now.

There's already MIPS support for something like this in GDB. 
Additionally, PPC support was posted.  And, someone posted v8plus
support for Solaris (three or four months ago?).  Don't remember what
became of that.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-05-12 22:32 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
2006-05-12 22:32     ` David S. Miller
2006-05-12 22:42       ` Daniel Jacobowitz [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=20060512223213.GA20204@nevyn.them.org \
    --to=drow@false.org \
    --cc=davem@davemloft.net \
    --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