Hi Keith,
> The stdlib is organized to take advantage of hardware instructions when
they are available and falls back to portable Go code when they aren't.
You actually answered my question == the ASM is the latest optimization
direction. So the desgin sequences are always:
1. Pure software
On Thursday, November 10, 2022 at 1:59:11 PM UTC-8 David Pacheco wrote:
> Hi Keith,
>
> Thanks for the helpful (and quick) reply! I gather you're right about not
> applying checkptr to Go's own test suite. I applied your patch, tried
> again, and started hitting failures in tests that were
I'm not sure exactly what the question is that you're asking here. "latest
and right optimization direction" doesn't make any sense to me.
The stdlib is organized to take advantage of hardware instructions when
they are available and falls back to portable Go code when they aren't.
It sounds to
Hi Keith,
Thanks for the helpful (and quick) reply! I gather you're right about not
applying checkptr to Go's own test suite. I applied your patch, tried
again, and started hitting failures in tests that were written for specific
past issues. These seem like false positives.
Do you have
That's correct. The runtime has a simple heuristic for avoiding zeroing but
it's far from perfect. As a result, a ballast is inherently always going to
be a little risky. This is especially true on some platforms, such as
Windows, since there's no way to avoid marking the memory as committed
Thank you!
tbh, I am a bit audacious by taking `//go:instrument`. But I think if
official Go toolchain starts to use `//go:instrument` or more people raise
concerns, I would definitely switch to something different.
Taking a note on your feedback. Will monitor for more comments about this.
--
Interesting
As a note, directive comments should be of the form `//toolname:directive`,
meaning the `//go:` prefix should be reserved for the `go` toolchain itself.
- sean
On Thu, Nov 10, 2022 at 4:07 PM Nikolay Dubina
wrote:
> *What?*
>
> Tool for automatic instrumentation of OpenTelemetry
*What?*
Tool for automatic instrumentation of OpenTelemetry Traces of all functions
and methods.
https://github.com/nikolaydubina/go-instrument
*Why?*
It is laborious to add tracing code to every function manually. The code
repeats 99% of time. Other languages can either modify code or have
> Who are the Go maintainers?
In this context, anyone who is part of the "approvers" group on
the Go gerrit instance (https://go-review.googlesource.com). The group
itself and the list of its members are not publicy visible, I believe.
> Is this the same set of people as
Thank you for your answer, it is clear now.
wtorek, 8 listopada 2022 o 13:38:33 UTC+1 ren...@ix.netcom.com napisał(a):
> To answer the rest of the question, since they are premptable they can be
> resumed on any thread. Go tries to use the same thread for performance but
> will issue memory
10 matches
Mail list logo
