From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 Go 386
Date: Sat, 25 May 2013 08:53:35 -0400 [thread overview]
Message-ID: <ccd90526bc0bc87c1fb9efd0341f90bb@kw.quanstro.net> (raw)
In-Reply-To: <1254af8db321f876dc44170675d6df34@proxima.alt.za>
On Sat May 25 01:50:51 EDT 2013, lucio@proxima.alt.za wrote:
> I've seen this before, although by now I've seen so many errors crop
> up that I can't recall them all.
>
> >> === RUN TestErrors-2
> >> template.test 289408: suicide: sys: floating point in note handler pc=0x0001e9c7
> >> exit status: 'template.test 289408: sys: floating point in note
> >> handler pc=0x0001e9c7'
> >> FAIL html/template 0.213s
> >
> > acid: stk()
> > runtime.memmove(to=0x106dd000,fr=0x30887660,n=0x2c)+0x107
> > /usr/glenda/src/go/src/pkg/runtime/memmove_386.s:145
> > runtime.sighandler(s=0x30887660,v=0x308876e4,gp=0x106d31b0)+0x126
> > /usr/glenda/src/go/src/pkg/runtime/os_plan9_386.c:67
> > runtime.sigtramp(ureg=0x30887660,note=0x106d31b0)+0x44
> > /usr/glenda/src/go/src/pkg/runtime/sys_plan9_386.s:161
> > 0x308876e4 ?file?:0
> > acid:
>
> I am surprised, but also relieved that we have a resproducible mistake
> outside the run.rc scope. We can focus on that.
this is not surprising. the backtrace and error seem to tell us everything
we need to know. go appears doing floating point in a note handler,
which is not legal in plan 9.
checking the code quickly from here
http://code.google.com/p/go/source/browse/src/pkg/runtime/memmove_386.s
we have
144 move_33through64:
145 MOVOU (SI), X0
which is indeed floating point in memmove. a quick fix would be to
comment out line 47 and make line 48 an unconditional jump.
47 // TESTL $0x4000000, runtime·cpuid_edx(SB) // check for sse2
48 JMP nosse2 // JEQ nosse2
- erik
next prev parent reply other threads:[~2013-05-25 12:53 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
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 [this message]
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=ccd90526bc0bc87c1fb9efd0341f90bb@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).