Re: [go-nuts] Race detector plus Cgo via binutils extld on arm64?

n Tue, Nov 23, 2021 at 2:34 AM Neil Schellenberger < neilschellenber...@gmail.com> wrote: > Thank you very much, Ian, for your insight. > > Unfortunately, after several more hours of fiddling, I still can't > convince it to work. I assume it's something to do with

Re: [go-nuts] Race detector plus Cgo via binutils extld on arm64?

Thank you very much, Ian, for your insight. Unfortunately, after several more hours of fiddling, I still can't convince it to work. I assume it's something to do with our (admittedly somewhat complicated) build environment/toolchain rather than a core Go problem, but I can't figure out what/how.

Re: [go-nuts] Timer.Reset() (again...)

Thank you very much for confirming that, Ian! FWIW the scenario is very roughly along the lines of a "best effort re-configurable" timeout for a work loop: timeout := <-timeoutConfigC timer := time.NewTimer(timeout) defer timer.Stop() for { select { case timeout = <-timeoutConfigC: t

[go-nuts] Timer.Reset() (again...)

Hi Folks, I am almost certainly overthinking this or in some other way "doing it wrong"--so please (dis)abuse me. The Timer.Reset() documentation reads (in part) "Reset should be invoked only on stopped or expired timers with drained channels." Am I correct in understanding that "should" in th

Re: [go-nuts] cgo behaviour change between go1.11.10 and go1.12.5

Sorry for the delay in responding. Filed as https://github.com/golang/go/issues/32579. On Tue, Jun 11, 2019 at 1:21 AM Ian Lance Taylor wrote: > On Mon, Jun 10, 2019 at 9:14 PM Neil Schellenberger > wrote: > > > > When upgrading our build container from 1.11.10 to 1.12.5, s

[go-nuts] cgo behaviour change between go1.11.10 and go1.12.5

Hi Folks, When upgrading our build container from 1.11.10 to 1.12.5, some of our tests failed in a surprising way. I've boiled down the issue to this short example code fragment. package main // #include // struct S { unsigned char data[18]; }; import "C" import "unsafe" func main() { var a

[go-nuts] Build constraints and preceding non-line comments

Hi Folks, The documentation of build constraints says, in part (emphasis mine): Constraints may appear in any kind of source file (not just Go), but they > must appear near the top of the file, *preceded only by blank lines and > other line comments*. The c