On Monday, 18 July 2016 19:37:46 UTC+3, ondrej...@gmail.com wrote:
>
> I think this pretty much covers it
>
> _, err := VirtualProtect(fn.body, 0x40)
> if err != nil {
> panic(err)
> }
>
> // OH GOD WHAT HAVE I DONE???
> type callstub struct{ fn func(*Memory) }
>
> Excellent and worrying
I think this pretty much covers it
_, err := VirtualProtect(fn.body, 0x40)
if err != nil {
panic(err)
}
// OH GOD WHAT HAVE I DONE???
type callstub struct{ fn func(*Memory) }
Excellent and worrying work :-) A 2x difference between interpreted and
native is pretty rad. It strongly remind
Impressive AND aggressive. ;-)
From: on behalf of Egon
Date: Monday, July 18, 2016 at 9:07 AM
To: golang-nuts
Cc: ,
Subject: Re: [go-nuts] Re: An efficient runtime expression evaluation
On Monday, 18 July 2016 13:27:09 UTC+3, Michael Jones wrote:
Anything much faster than this needs
On Monday, 18 July 2016 13:27:09 UTC+3, Michael Jones wrote:
>
> Anything much faster than this needs vector operations in the interpreter
> so the “get to the OP function” overhead is once per time series rather
> than once per element in the series.
>
I managed to make it a little faster https
Anything much faster than this needs vector operations in the interpreter so
the “get to the OP function” overhead is once per time series rather than once
per element in the series.
From: on behalf of Egon
Date: Monday, July 18, 2016 at 1:32 AM
To: golang-nuts
Cc:
Subject: [go-nuts] Re:
