From: Greg Lindahl <lindahl@keyresearch.com>
To: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: your mail
Date: Sat, 26 Oct 2002 13:32:09 -0700 [thread overview]
Message-ID: <20021026133209.B2153@wumpus.attbi.com> (raw)
In-Reply-To: <37A3C2F21006D611995100B0D0F9B73CBFE312@tnint11.telogy.design.ti.com>; from nmckee@telogy.com on Sat, Oct 26, 2002 at 03:48:27PM -0400
On Sat, Oct 26, 2002 at 03:48:27PM -0400, Zajerko-McKee, Nick wrote:
> I'm porting some code from x86 to mips(32) and noticed that in
> include/asm-mips/siginfo.h differs from include/asm-i386/siginfo.h in the
> order of elements of the sigchld structure. Was this an oversight or a
> design decision? I would think that it would be desirable to be almost the
> same as the x86 for userland ease of portability...
User programs normally get recompiled, so anything using the proper
includes IS portable.
The issue only appears if you are using binary translation of x86
programs on mips. For example, this is one:
http://www.transitives.com/products.htm
For this, you need to write a system call translation layer which
rearranges things appropriately. An existing example is the o32 layer
in mips64, and soon the n32 layer in mips64.
-- greg
next prev parent reply other threads:[~2002-10-26 20:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 19:48 Zajerko-McKee, Nick
2002-10-26 20:08 ` your mail Daniel Jacobowitz
2002-10-26 20:32 ` Greg Lindahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-06 5:52 Jiaxun Yang
2020-05-07 11:00 ` your mail Thomas Bogendoerfer
2018-08-27 14:50 Christoph Hellwig
2018-08-31 20:23 ` your mail Paul Burton
2018-03-09 15:12 [PATCH 00/14] Enable SD/MMC on JZ4780 SoCs Ezequiel Garcia
2018-03-09 15:12 ` [PATCH 08/14] mmc: jz4740: Add support for the JZ4780 Ezequiel Garcia
2018-03-09 17:51 ` [PATCH 08/14] mmc: jz4740: Add support for the JZ4780, Paul Cercueil
2018-03-09 22:31 ` your mail James Hogan
2018-03-09 22:31 ` James Hogan
2008-01-22 0:00 (no subject) Thiemo Seufer
2008-01-28 17:51 ` your mail Ralf Baechle
2005-04-28 19:15 Bryan Althouse
2005-04-29 11:02 ` your mail Ralf Baechle
2003-04-18 0:08 Dennis Castleman
2003-04-17 17:53 Dennis Castleman
2003-04-17 18:17 ` your mail Jun Sun
2003-04-17 20:15 ` Greg Lindahl
2003-04-18 0:03 ` Ralf Baechle
2003-03-29 6:54 Avinash S.
2003-03-29 7:25 ` your mail Thiemo Seufer
2001-10-03 14:28 Marian Kafadarov
2001-10-03 15:52 ` your mail Martin Schulze
[not found] <5.0.0.25.0.20010404172906.00a4bce8@vmspop.isc.rit.edu>
2001-04-04 21:37 ` Matthew Fredrickson
2001-04-05 5:08 ` Ralf Baechle
2001-02-15 0:27 Deepa Suresh
2001-02-15 11:03 ` your mail Geert Uytterhoeven
2001-01-04 1:36 John Van Horne
2001-01-04 15:36 ` your mail Ralf Baechle
2001-01-04 16:22 ` Maciej W. Rozycki
2001-01-04 16:40 ` Joe deBlaquiere
2001-01-04 17:13 ` Ralf Baechle
2001-01-04 17:46 ` Joe deBlaquiere
2001-01-04 18:12 ` Maciej W. Rozycki
2001-01-04 17:18 ` Maciej W. Rozycki
1997-08-09 17:16 Vincent Renardias
1997-08-09 17:41 ` your mail Ralf Baechle
1997-08-09 17:41 ` Ralf Baechle
1997-08-09 19:40 ` Vincent Renardias
1997-08-09 19:42 ` Ralf Baechle
1997-08-09 19:42 ` Ralf Baechle
1997-08-09 21:05 ` Vincent Renardias
1997-08-09 21:11 ` Ralf Baechle
1997-08-09 21:11 ` Ralf Baechle
1997-08-10 2:57 ` Vincent Renardias
1997-08-09 22:53 ` Mike Shaver
1997-08-09 22:53 ` Mike Shaver
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=20021026133209.B2153@wumpus.attbi.com \
--to=lindahl@keyresearch.com \
--cc=linux-mips@linux-mips.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