From: Peter Bergner <bergner@borg.umn.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Microsoft and Xenix.
Date: Wed, 27 Jun 2001 08:43:55 -0500 [thread overview]
Message-ID: <20010627084355.A57645@brule.borg> (raw)
In-Reply-To: <E15DZbq-0008D8-00@roo.home> <01062310075401.00696@localhost.localdomain> <83WVxfbXw-B@khms.westfalen.de> <01062611162702.12583@localhost.localdomain> <20010626172654.B588@munchkin.spectacle-pond.org>
In-Reply-To: <20010626172654.B588@munchkin.spectacle-pond.org>
First off, my apologies for posting this from my non-work email address.
>From my .sig below, you'll see I work for IBM, Rochester.
Rob Landley wrote:
: The AS400 seems to be based out of Austin. We hear a lot about it around
: here...
and...
Michael Meissner wrote:
: Ummm, the AS/400 was based out of Rochester, Minnesota at least initially.
[snip]
: Now that AS/400's are based on special PowerPC's, the home may have moved
: to Austin, which is the PowerPC/AIX center.
The AS/400 (now named iSeries) is and always has been produced in
Rochester Minnesota. The RS/6000 (now named pSeries) is designed
in Austin. Both the AS/400 and the RS/6000 are manufactured in
Rochester. As of some model which escapes me now, both AS/400 and
RS/6000 computers use the *same* PowerPC processor. The only
difference is that the AS/400 runs the processor in "tags active"
mode (ie, the 65th tag bit enabled). The first PowerPC processors
used in the AS/400 was designed here in Rochester. Follow-ons were
designed in Austin.
Kai Henningsen wrote:
: ISTR there's a gcc port for the AS/400.
Due to the fact that the AS/400 has 1 address space shared by all
processes, several restrictions have been implemented. The main
restriction regarding your statement above is that *all* code that runs
on the AS/400 is compiled by the "trusted" translator (an exception
would be our Java JIT). This means you cannot create a binary with gcc
and hope to run it on the AS/400. However, you may use gcc to produce
MI instructions which can then be passed to the trusted translator.
Peter
--
Peter Bergner
SLIC Optimizing Translator Development / Linux PPC64 Kernel Development
IBM Rochester, MN
bergner@us.ibm.com
next prev parent reply other threads:[~2001-06-27 13:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 22:41 Microsoft and Xenix Alan Chandler
2001-06-23 14:07 ` Rob Landley
2001-06-24 0:13 ` Michael Alan Dorman
2001-06-24 14:18 ` Rob Landley
2001-06-25 1:45 ` Jeff Dike
2001-06-24 20:51 ` Rob Landley
2001-06-24 0:49 ` John Adams
2001-06-24 14:25 ` Rob Landley
2001-06-24 2:47 ` Eric W. Biederman
2001-06-24 10:36 ` Rob Landley
2001-06-24 22:20 ` [OT] " Daniel Phillips
2001-06-25 3:38 ` Michal Jaegermann
2001-06-24 22:41 ` Chris Meadors
2001-06-24 21:13 ` Microsoft and Xenix - Now there's a mailing list for this discussion Rob Landley
2001-06-25 0:55 ` Microsoft and Xenix William T Wilson
2001-06-25 17:11 ` asmith
2001-06-25 18:18 ` Robert J.Dunlop
2001-06-25 3:17 ` Eric W. Biederman
2001-07-02 10:04 ` Juan Quintela
2001-06-25 19:23 ` Kai Henningsen
2001-06-26 15:16 ` Rob Landley
2001-06-26 21:26 ` Michael Meissner
2001-06-27 8:09 ` Geert Uytterhoeven
2001-06-27 18:07 ` Peter De Schrijver
2001-06-27 13:43 ` Peter Bergner [this message]
2001-06-28 21:11 ` Thomas Dodd
2001-06-23 17:57 ` Mike Jagdis
2001-06-23 17:11 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2001-06-24 2:41 Wayne.Brown
2001-06-24 3:07 ` Mike Castle
2001-06-24 14:44 ` Rob Landley
2001-06-25 15:13 ` Joel Jaeggli
2001-06-25 14:17 ` Rob Landley
2001-06-25 19:57 ` Erik Mouw
2001-06-27 2:10 ` Steve Underwood
2001-06-25 19:30 ` Kai Henningsen
2001-06-25 20:19 ` asmith
2001-06-24 14:32 ` Rob Landley
2001-06-24 2:59 Wayne.Brown
2001-06-25 2:51 Wayne.Brown
2001-06-24 23:21 ` Rob Landley
2001-06-25 17:14 ` asmith
2001-06-25 14:54 ` Rob Landley
2001-06-25 17:29 Wayne.Brown
2001-06-26 3:21 Jocelyn Mayer
2001-06-26 15:15 ` Joel Jaeggli
2001-06-26 16:15 ` Daniel Phillips
2001-06-26 16:42 ` Rob Landley
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=20010627084355.A57645@brule.borg \
--to=bergner@borg.umn.edu \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox