> On 23 Feb 2016, at 18:31, lu...@proxima.alt.za wrote:
>
>> A proper duffcopy/duffzero/memmove is also an option.
>
> The adjective "proper" is revealing. I vote for that.
>
> Lucio.
>
>
It’s a bit out of my usual area of expertise, however. I have no idea what
benchmark they have been ru
> A proper duffcopy/duffzero/memmove is also an option.
The adjective "proper" is revealing. I vote for that.
Lucio.
A proper duffcopy/duffzero/memmove is also an option.
Best regards,
Kenny Levinsen
> On 23. feb. 2016, at 18.02, erik quanstrom wrote:
>
>> On Tue Feb 23 07:55:26 PST 2016, kennylevin...@gmail.com wrote:
>> A benchmark was supposedly made of the new duffcopy/duffzero which claimed
>> significa
On Tue Feb 23 07:55:26 PST 2016, kennylevin...@gmail.com wrote:
> A benchmark was supposedly made of the new duffcopy/duffzero which claimed
> significant speedup for larger copies:
> https://github.com/golang/go/commit/5cf281a9b791f0f10efd1574934cbb19ea1b33da
>
> I have no clue whether this hol
A benchmark was supposedly made of the new duffcopy/duffzero which claimed
significant speedup for larger copies:
https://github.com/golang/go/commit/5cf281a9b791f0f10efd1574934cbb19ea1b33da
I have no clue whether this holds true or not. My intention to reenable
duffcopy and continue to use duf
On Tue Feb 23 02:36:41 PST 2016, kennylevin...@gmail.com wrote:
> Ah, no - it is not a system-wide adjustment, but adjustment of the plan9
> specific runtime.sighandler implementation and everything called by it
> directly. Notes that don't exit the process are queued and should run outside
> th
Ah, no - it is not a system-wide adjustment, but adjustment of the plan9
specific runtime.sighandler implementation and everything called by it
directly. Notes that don't exit the process are queued and should run outside
the actual note handler.
I think the "magic" code will be isolated, and m
Well, avoiding XMM registers in duffcopy/duffzero is one solution, but I was
thinking of working around them entirely in code called from the note handler,
so that duffcopy/duffzero can operate as intended on plan9, rather than
littering the compiler with OS conditionals.
It puts some restricti
For those interested in the matter, I have opened
https://github.com/golang/go/issues/14471
I mention potentially reenabling duffcopy by writing some magic note handler
code that avoid the regular copy and zero optimizations, but I’m not entirely
sure if that’s a plausible path. If it is, I thi
