From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] broken floating point exceptions and fpregs
Date: Sat, 25 May 2013 21:21:31 +0200 [thread overview]
Message-ID: <9406F4AD-427A-462F-B751-74A22C3A1630@lsub.org> (raw)
In-Reply-To: <2a810e5901ddf3cbde877071719c103e@kw.quanstro.net>
did not publish it yet, but we have what
could be called a nix mark II, comes
with a new mount table and a fossil
speaking 9pix, plus a new scheduler.
It does not have al the stuff like graphics in the modified mark I nix
you have, but, the new stuff should be
easy to use on it.
give us a bit more time and we will put
the new bits somewhere.
hth
On May 25, 2013, at 5:02 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> On Sat May 25 09:59:39 EDT 2013, khm-9@intma.in wrote:
>> On Sat, May 25, 2013 at 09:47:05AM -0400, erik quanstrom wrote:
>>>
>>> why don't we just let the 386 kernel rest in peace and use
>>> 64-bit for sse?
>>
>> Let's all go buy new computers instead of using the ones we have?
>
> x86_64 has been around since 2003, and on nearly every x86 machine for
> the last 8 years. sse2 has been around since 2001. there is not a large
> percentage of currently-running x86 machines that have sse2 but do not have
> x64-bit extensions, and this percentage is generally decreasing.
>
> i put sse2 in the 386 kernel a few years ago, before the compilers supported
> it. this was to support a linuxemu project. the linux tools needed sse.
>
> however, when it came to putting sse2 into a general kernel—and that
> includes answering questions cinap is posing, like how do we deal with
> different abis in the debugger, etc.—it seemed more disruption than it
> was worth. now that the 64-bit kernel is real, and supports even low-end
> hardware like atom, i would rather concentrate on making
> the 64-bit kernel better.
>
> - erik
next prev parent reply other threads:[~2013-05-25 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 21:29 cinap_lenrek
2013-05-25 2:10 ` cinap_lenrek
2013-05-25 13:47 ` erik quanstrom
2013-05-25 13:58 ` Kurt H Maier
2013-05-25 15:02 ` erik quanstrom
2013-05-25 15:40 ` Kurt H Maier
2013-05-25 15:59 ` erik quanstrom
2013-05-25 19:21 ` Francisco J Ballesteros [this message]
2013-05-26 6:00 ` lucio
2013-05-26 8:40 ` Francisco J Ballesteros
2013-05-26 5:57 ` lucio
2013-05-27 3:51 ` Anthony Sorace
2013-05-27 5:35 ` lucio
2013-05-25 14:54 ` cinap_lenrek
2013-05-25 15:00 ` erik quanstrom
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=9406F4AD-427A-462F-B751-74A22C3A1630@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@9fans.net \
/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).