From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: s390x: correct core file register layout
Date: Tue, 03 Jun 2003 05:49:00 -0000 [thread overview]
Message-ID: <vt2of1fpv6v.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <vt24r3mywfe.fsf@zenia.red-bean.com>
I've committed this patch. (But as always, I'd be happy to revise it
if someone had nice suggestions.)
Jim Blandy <jimb@redhat.com> writes:
> 2003-05-23 Jim Blandy <jimb@redhat.com>
>
> * s390-nat.c (supply_gregset, fill_gregset): On the s390x, the
> elements of gregset_t are 64 bits each, but access registers
> are still 32 bits, so they're packed two per gregset_t
> element. Unpack/pack them properly.
prev parent reply other threads:[~2003-06-03 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 6:58 Jim Blandy
2003-06-03 0:59 ` Michael Snyder
2003-06-03 5:48 ` Jim Blandy
2003-06-03 13:03 ` Daniel Jacobowitz
2003-06-03 16:59 ` Jim Blandy
2003-06-03 5:49 ` Jim Blandy [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=vt2of1fpv6v.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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