From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 24 May 2013 09:50:40 -0400
To: 9fans@9fans.net
Message-ID: <41323f23fe9d683a6ff015df932b4f82@kw.quanstro.net>
In-Reply-To: <CAH7AAvpLjmkt8U6M3gmsvt5o+2FO7d8VFWMyQKxjfhkXa-VZyw@mail.gmail.com>
References: <CAH7AAvpLjmkt8U6M3gmsvt5o+2FO7d8VFWMyQKxjfhkXa-VZyw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Plan 9 Go 386
Topicbox-Message-UUID: 5b509e8e-ead8-11e9-9d60-3106f5b1d025

>
> Compiling the go tool chain with sse2 under VMware yields broken
> tools, and building with GO386=387, consistently breaks the tests. On
> bare metal, all tests except net/http pass most of the time. When a
> test fails I get the following errors:

which tests does it break?  ?c compile -0. as 0 (which is incorrect),
and print(2)'s %g and %f print -0. as 0.  could this or other bits of
non-ieee conformance in the system be the real issue?

>  From the test:
> <test> <pid>: suicide: sys: trap: fault write addr=0xfffffffc pc=0x0001e6ea
> panic: runtime error: index out of range

i can't imagine how bad sse would lead to accessing address -4.

this looks like the problem rob fixed the other week.

- erik