From: Paul Brook <paul@nowt.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [7192] Fix target_siginfo ordering for MIPS.
Date: Tue, 21 Apr 2009 00:59:41 +0000 [thread overview]
Message-ID: <E1Lw4Kr-0006YF-FT@cvs.savannah.gnu.org> (raw)
Revision: 7192
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=7192
Author: pbrook
Date: 2009-04-21 00:59:40 +0000 (Tue, 21 Apr 2009)
Log Message:
-----------
Fix target_siginfo ordering for MIPS.
Signed-off-by: Paul Brook <paul@codesourcery.com>
Modified Paths:
--------------
trunk/linux-user/syscall_defs.h
Modified: trunk/linux-user/syscall_defs.h
===================================================================
--- trunk/linux-user/syscall_defs.h 2009-04-20 23:55:57 UTC (rev 7191)
+++ trunk/linux-user/syscall_defs.h 2009-04-21 00:59:40 UTC (rev 7192)
@@ -504,9 +504,15 @@
#define TARGET_SI_PAD_SIZE ((TARGET_SI_MAX_SIZE/sizeof(int)) - 3)
typedef struct target_siginfo {
+#ifdef TARGET_MIPS
int si_signo;
+ int si_code;
int si_errno;
+#else
+ int si_signo;
+ int si_errno;
int si_code;
+#endif
union {
int _pad[TARGET_SI_PAD_SIZE];
reply other threads:[~2009-04-21 0:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Lw4Kr-0006YF-FT@cvs.savannah.gnu.org \
--to=paul@nowt.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).