From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>,
Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: Re: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit
Date: Mon, 28 Jun 2004 14:51:00 -0000 [thread overview]
Message-ID: <40E02528.7060906@gnu.org> (raw)
In-Reply-To: <20040627184026.GC795@tausq.org>
>>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.
Lets expand the list (you can get much of this from sizeof.exp):
- sizeof (saved register)
- sizeof (int)
- sizeof (long)
- sizeof (void *)
- sizeof (long long)
- sizeof (ptrace/ktrace register)
> The hppa target naming conventions are a bit weird (to me, at least)
I'm guessing that we're missing one:
hppa1.x executable. Since michael stated that registers were being
saved as 4-bytes, I think we're looking at this one.
> 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)
This is sounding a lot like MIPS N32:
8 - sizeof (saved register)
4 - sizeof (int)
4 - sizeof (long)
4 - sizeof (void *)
8 - sizeof (long long)
8 - sizeof (ptrace/ktrace register)
> 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.
This is getting into 32x64 - there be dragons.
Andrew
next prev parent reply other threads:[~2004-06-28 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 4:20 Michael Elizabeth Chastain
2004-06-27 18:40 ` Randolph Chung
2004-06-27 18:57 ` Daniel Jacobowitz
2004-06-28 14:51 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-26 23:28 Michael Elizabeth Chastain
2004-06-27 1:52 ` Andrew Cagney
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=40E02528.7060906@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=randolph@tausq.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).