From: Mario Smarduch <cms063@email.mot.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] One little, two little, three little endian...
Date: Fri, 15 Nov 2002 16:11:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805453@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805439@msgid-missing>
David Mosberger wrote:
> Hi Gavin,
>
> >>>>> On Thu, 14 Nov 2002 16:52:13 -0800, "Gavin Scott" <gavin@allegro.com> said:
>
> Gavin> Hello list, I want a big endian version of Linux for IPF.
> Gavin> Just how crazy am I?
>
> Very! ;-)
>
> Seriously though: running big-endian processes is the easy part, the
> hard part is developing (& maintaining) big-endian versions of all
> libraries. Not only is it a lot of work, but it would also fragment
> the ia64 linux market, so I'd consider it a Bad Thing (TM).
>
> Gavin> Of course both MPE/iX and HP-UX are big-endian environments,
> Gavin> and many of the people I talk to would be very interested in
> Gavin> having an endian-compatible Linux that would run on big
> Gavin> (i.e. IA-64) HP servers. For this group, x86 compatibility
> Gavin> is probably a non-issue.
>
> It would be a lot easier to add an hp-ux compatibility layer on top of
> ia64 linux. The layer would emulate the (big-endian) hp-ux system
> calls and then you would install the big-endian hp-ux libraries on top
> of that (e.g., in the /emul/ia64-hpux/ tree). Of course, I'm ignoring
> legal issues here as copying the hp-ux libraries would presumably
> require some sort of license. But legal issues aside, this is doable
> and has been done many times before (e.g., alpha linux can run (some)
> Tru64 binaries, sparc linux can run sunos/solaris(?) binaries, etc.).
David a quick question. Even though the library problem is overcomed,
how would signal handling be accomplished by an application
running in big-endian. Doesn't the kernel fill in the siginfo and context
while runing in little endian?
- Mario.
>
>
> Gavin> I'm interested in any comments that come to mind. I'm most
> Gavin> interested in just how complex the task would be from a
> Gavin> technical point of view, either to make the system buildable
> Gavin> either way, or possibly supporting a per-process endian bit
> Gavin> (which would be cool, but probably a lot more work).
>
> Actually, adding a per-process endian bit would be easy. In fact,
> even without, a little-endian program can turn on the big-endian bit
> as long as it's prepared to deal with the consequences. The hard part
> is really the libraries.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2002-11-15 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 0:52 [Linux-ia64] One little, two little, three little endian Gavin Scott
2002-11-15 1:55 ` David Mosberger
2002-11-15 2:25 ` Don Dugger
2002-11-15 2:28 ` Randolph Chung
2002-11-15 3:41 ` Grant Grundler
2002-11-15 3:50 ` Don Dugger
2002-11-15 4:47 ` Randolph Chung
2002-11-15 13:15 ` Matthew Wilcox
2002-11-15 16:11 ` Mario Smarduch [this message]
2002-11-15 16:58 ` David Mosberger
2002-11-15 17:44 ` Rich Altmaier
2002-11-15 17:56 ` Gavin Scott
2002-11-15 17:57 ` Gavin Scott
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=marc-linux-ia64-105590709805453@msgid-missing \
--to=cms063@email.mot.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.