9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 Go 386
Date: Fri, 24 May 2013 09:50:40 -0400	[thread overview]
Message-ID: <41323f23fe9d683a6ff015df932b4f82@kw.quanstro.net> (raw)
In-Reply-To: <CAH7AAvpLjmkt8U6M3gmsvt5o+2FO7d8VFWMyQKxjfhkXa-VZyw@mail.gmail.com>

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



  parent reply	other threads:[~2013-05-24 13:50 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 [this message]
2013-05-24 14:29   ` lucio
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=41323f23fe9d683a6ff015df932b4f82@kw.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).