Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Avoid MIPS port breakage on large registers
Date: Mon, 21 May 2007 14:09:00 -0000	[thread overview]
Message-ID: <20070521140859.GA10409@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0705211456420.8263@blysk.ds.pg.gda.pl>

On Mon, May 21, 2007 at 03:01:30PM +0100, Maciej W. Rozycki wrote:
> On Mon, 21 May 2007, Daniel Jacobowitz wrote:
> 
> > I am about to post target-described register support for the MIPS
> > port.  One thing I noticed while testing it was that "info registers"
> > went off into the woods on O32 when I added an extra 64-bit register;
> > there's an unsigned loop until regsize - abi_regsize, which is
> > supposed to catch 32-bit registers on N64, but runs almost forever
> > given a 64-bit integer register on O32.  This patch just prints such
> > registers on their own row.
> 
>  Hmm, out of curiosity: what kind of 64-bit register have you got on o32?  

It's the $restart "register" that I just posted support for.
Gdbserver doesn't know the program's ABI, so a mips64-linux gdbserver
always reports 64-bit registers.  GDB knows to translate $pc to
32-bit, but mips-tdep.c doesn't know anything about special handling
for $restart (and I didn't think it was important to add, with this
bug fixed).

The register only ever holds internal errno values (0 or 512-514).

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-05-21 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 13:05 Daniel Jacobowitz
2007-05-21 14:01 ` Maciej W. Rozycki
2007-05-21 14:09   ` Daniel Jacobowitz [this message]
2007-06-13 17:25 ` 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=20070521140859.GA10409@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    /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