This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit
- From: Daniel Jacobowitz <drow at false dot org>
- To: Randolph Chung <randolph at tausq dot org>
- Cc: Michael Elizabeth Chastain <mec dot gnu at mindspring dot com>, cagney at gnu dot org,gdb at sources dot redhat dot com
- Date: Sun, 27 Jun 2004 14:57:00 -0400
- Subject: Re: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit
- References: <20040627042052.CABC44B104@berman.michael-chastain.com> <20040627184026.GC795@tausq.org>
On Sun, Jun 27, 2004 at 11:40:26AM -0700, Randolph Chung wrote:
> > ac> What's the ABI wordsize - the size of a register pushed onto the stack?
> > ac> "info registers" should be using that register size and looking at the
> > ac> HP/PA code, that appears to be the case.
> >
> > It's 4 bytes, all right.
>
> The hppa target naming conventions are a bit weird (to me, at least)
>
> hppa2.0w-*-* is a 32-bit target, however the w means that you can use
> 64-bit registers and the pa2.0 64-bit opcodes (ldd, std, etc)
>
> hppa64-*-* is the 64-bit target.
>
> > The funny thing is, gdb 6.1.1 "maint print registers" says that
> > r19 is 4 bytes long, but "info reg r19" has special code to print
> > all 8 bytes of it.
> >
> > I'm still kinda dubious, but if it's okay with randolph that the
> > debugger quietly operates in 32-bit mode, it's okay with me.
> > I would do something like this:
>
> Yes, i think this is ok.
If hppa2.0w-*-* is a 32-bit target (pointers, I assume you mean), but
has 64-bit registers, then the regcache for it should indicate that
registers are eight bytes wide... maybe this isn't a regression or a
surprise, but it's definitely better if you show all bits.
--
Daniel Jacobowitz