From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Sane Architectures
Date: Mon, 26 Mar 2001 18:07:56 -0500 [thread overview]
Message-ID: <3ABFCBCC.30700@lycosmail.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10103261752260.23483-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>> Are there any architectures that are simple (sane) to implement sftw on?
>
>
> sftw? software? yes: portable C/C++ is a fine platform.
Not really the platform, but the architecture, from a C/C++ compiler and
kernel/asm/lowlevel lang development standpoint
>
>> The i386 is plagued by it's 16-bit (arguably its 8 or even 4 bit) past.
>
>
> I wonder what you mean by that. it's ia32's accumulator-based
> architecture, and stack-based FPU that "plague" it, neither of which
> has anything to do with bitness. or are you actually talking about
> instruction encoding?
the limited number of registers (3 bits allocated, IIRC) which limits
the number to 8 minus CS,DS,IP; meaning only 5 GPRs, the requirement of
an (antiquated) BIOS (design), 16-bit bootstrap
>
>> This can include architectures like the IA64 & the upcoming x86-64. Just
>> looking for something with lots of GPR's, sane MM support, etc.
>
If not lots of GPRs, but at least enough to be able to allocate sanely.
>
> alpha? mips?
Yes, I just didn't feel like listing all arch's. Plus, (ducks) the MIPS
is no longer supported by Windoze, and I rarely see any discussion on lk
about this arch, and I forgot about Alpha for a minute.
I admit that I likely look like an idiot right now, and I am not
intending to insult anyone, just curious about this.
next parent reply other threads:[~2001-03-26 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10103261752260.23483-100000@coffee.psychology.mcmaster.ca>
2001-03-26 23:07 ` Adam Schrotenboer [this message]
2001-03-27 0:28 ` [OT] Sane Architectures Matthew Fredrickson
2001-03-26 22:41 Adam Schrotenboer
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=3ABFCBCC.30700@lycosmail.com \
--to=ajschrotenboer@lycosmail.com \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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