Hi all,
I'm currently writing a Golang + CGO program, and will use posix ucontext
in CGO. Since all my core logic will be in the bind function of ucontext,
we should catch up all the bad code. And I test it by accessing to the null
pointer, which give me totally different behaviors that all
Hello,
Since I could not find the answer in the cgo documentation, I would really
appreciate if somebody could help me to understand why when I build cgo code
with calls to the shared library, the linker tries to find the shared library
even though it is instructed to build dynamic binary
Heh. Yes, it is only an "aim" I suppose.
Yes. My code is single threaded. I note that threading will be added to the
WASM spec in the near future so maybe there will be opportunity for me
there when the change is added to the Go compiler.
I'll put this issue to rest for now and revisit it in a
The cynic in me notes the use of "aims".
IIRC is single-threaded, do you know if your code is single- threaded too,
or does it use several core for decoding?
On Saturday, September 23, 2023 at 7:37:13 AM UTC+2 Stephen Illingworth
wrote:
> Comparison to native speeds is the key attraction of
