9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 Go 386
Date: Fri, 24 May 2013 16:29:19 +0200	[thread overview]
Message-ID: <92894a638b08c19f7d8ed12921c0198d@proxima.alt.za> (raw)
In-Reply-To: <41323f23fe9d683a6ff015df932b4f82@kw.quanstro.net>

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




  reply	other threads:[~2013-05-24 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 22:14 Christopher Nielsen
2013-05-23 23:25 ` Steve Simon
2013-05-24 13:50 ` erik quanstrom
2013-05-24 14:29   ` lucio [this message]
2013-05-25  1:11     ` Jeremy Jackins
2013-05-25  2:00       ` Skip Tavakkolian
2013-05-25  2:36         ` Jeremy Jackins
2013-05-25  3:06           ` Jeremy Jackins
2013-05-25  5:50             ` lucio
2013-05-25 12:53               ` erik quanstrom
2013-05-25 18:25                 ` Jeremy Jackins
2013-05-25  5:17       ` lucio

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=92894a638b08c19f7d8ed12921c0198d@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).