From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <92894a638b08c19f7d8ed12921c0198d@proxima.alt.za>
To: 9fans@9fans.net
Date: Fri, 24 May 2013 16:29:19 +0200
From: lucio@proxima.alt.za
In-Reply-To: <41323f23fe9d683a6ff015df932b4f82@kw.quanstro.net>
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: 5b5706ac-ead8-11e9-9d60-3106f5b1d025

> 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?

They could be significant, but only where floating point is involved,
the failures I noted do not have an obvious floating point component -
except when SSE2 is required and not available.

So let's start with a show of hands.  Who can consistently run the Go
build tests (run.rc --no-rebuild in $GOROOT/src after a successful
make.rc) without failure and what is the Plan 9 (i386) environment
applicable?

Factors I believe are relevant are CPU type, including SSE2
capabilities, which fork of Plan 9 (current Bell Labs
distribution/prior to the 21-bit Rune update (maybe), nix, 9atom,
9front, are there others?  I know 9vx is broken, sadly.), local
updates may be pertinent too.  Also, I'm assuming, with Christopher,
that we're dealing with Go "tip", if it's an older version, that may
point us in some useful direction.

Also, for the more adventurous, CL 7987044 (from memory - prompt me if
it's wrong) adds ARM capabilities, modulo some changes from Gorka I
have yet to identify.  I will be going off topic for a while, I need
to rebuild the local ESXi instance and that will probably take longer
than the weekend, so I can't promise much help until I'm done.  But I
will be interested in the outcome of this poll.

If you can, pass the request on, there may be people this message
can't reach.

Lucio.