From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b0503215b77460f6f7e993b5f6b8224f@proxima.alt.za>
To: 9fans@9fans.net
Date: Mon,  3 Jun 2013 19:04:30 +0200
From: lucio@proxima.alt.za
In-Reply-To: <39c6e4b135cec83b2095612a1e178536@ladd.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status)
Topicbox-Message-UUID: 6203206c-ead8-11e9-9d60-3106f5b1d025

> if by intent, you mean that go is using xmm registers as if they were
> general purpose registers, then the solution is to stop doing that.
> and there's such a patch already.

No, Go's intent is to minimise runtime surprises.  It is possible to
define signal (calling them notes does not change their nature)
handlers and nothing in the Go specifications compels the user not to
use floating point instructions in such handlers.  It would also not
be possible to enforce such restrictions in known implementations of
Go and that creates a conflict.  Unless I'm straying into areas I am
ignorant of, something needs to be done for Go and Plan 9 to coexist
amicably, the current conditions are prone to Go-incompatible
behaviour.

Solving the memmove() problem just puts the crisis off for a while.
Once Go is being used on Plan 9 and especially if a user expects
portability from more common platforms, this particular
incompatibility is likely to hurt.

++L