From: Thiemo Seufer <ths@networkno.de>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: gdb vs. gdbserver with -mips3 / 32bitmode userspace
Date: Tue, 31 Jan 2006 18:42:53 +0000 [thread overview]
Message-ID: <20060131184253.GA23753@networkno.de> (raw)
In-Reply-To: <20060131181414.GA8288@linuxtv.org>
On Tue, Jan 31, 2006 at 07:14:14PM +0100, Johannes Stezenbach wrote:
[snip]
> Yes, that's why I said I'm confused about mips_isa_regsize() vs.
> mips_abi_regsize().
>
> mips_abi_regsize() correctly says the register size is 32bit for o32,
> but mips_register_type() calls mips_isa_regsize(), not
> mips_abi_regsize(). That's why I chose to "fix" mips_isa_regsize().
>
> Or should mips_register_type() simply call mips_abi_regsize()?
Without having had a look at the code I think that's the right fix.
> Or is the correct fix to change gdbserver to transfer registers
> in mips_isa_regsize() size, i.e. 64bit for 64bit ISA?
> (But gdb would't use the upper 32bits of the registers anyway
> with o32 ABI, and this would be more complicated to fix.)
Thiemo
next prev parent reply other threads:[~2006-01-31 18:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 17:15 gdb vs. gdbserver with -mips3 / 32bitmode userspace Johannes Stezenbach
2006-01-31 17:36 ` Maciej W. Rozycki
2006-01-31 18:14 ` Johannes Stezenbach
2006-01-31 18:42 ` Thiemo Seufer [this message]
2006-01-31 19:23 ` Johannes Stezenbach
2006-02-01 19:07 ` Johannes Stezenbach
2006-02-01 19:20 ` Johannes Stezenbach
2006-02-01 16:44 ` Daniel Jacobowitz
2006-02-01 16:53 ` Maciej W. Rozycki
2006-02-01 17:26 ` Michael Uhler
2006-02-01 17:26 ` Michael Uhler
2006-02-01 19:24 ` Daniel Jacobowitz
2006-02-02 13:26 ` Ralf Baechle
2006-02-01 19:44 ` Johannes Stezenbach
2006-02-02 13:43 ` Ralf Baechle
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=20060131184253.GA23753@networkno.de \
--to=ths@networkno.de \
--cc=js@linuxtv.org \
--cc=linux-mips@linux-mips.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