From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: randolph@tausq.org (Randolph Chung)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix hppa_linux_sigtramp_frame_unwind_cache
Date: Sun, 14 Sep 2008 03:47:00 -0000 [thread overview]
Message-ID: <20080914034722.83F464E6A@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <1e3eba760809131944t7ce2b87ai94af49ba8074b901@mail.gmail.com> from "Randolph Chung" at Sep 13, 2008 07:44:09 pm
> The sigcontext structure looks like this:
>
> struct sigcontext {
> unsigned long sc_flags;
> unsigned long sc_gr[32];
> unsigned long long sc_fr[32];
> unsigned long sc_iasq[2];
> unsigned long sc_iaoq[2];
> unsigned long sc_sar;
> };
>
> I am positive that when I wrote this the structure got padded between
> sc_gr and sc_fr to keep the unsigned long long at a 8-byte boundary.
No, you are correct. The long long field will be aligned at an 8-byte
boundary. I will keep the pad.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
next prev parent reply other threads:[~2008-09-14 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 23:58 John David Anglin
2008-09-14 2:44 ` Randolph Chung
2008-09-14 3:47 ` John David Anglin [this message]
[not found] <no.id>
2008-09-15 2:24 ` John David Anglin
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=20080914034722.83F464E6A@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gdb-patches@sourceware.org \
--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