Re: [go-nuts] weird "index out of range" in strconv.formatBits

700, metronome wrote: > > > > Have you built with CGO_ENABLED=0? > > Building with CGO_ENABLED=0 succeeded, does that mean the binary's > > runtime behavior has nothing to do with CGO, deploying > > a CGO_ENABLED=0 binary online is not an option as well, for now (We >

Re: [go-nuts] weird "index out of range" in strconv.formatBits

:16 PM UTC+8 Dan Kortschak wrote: > On Wed, 2023-08-16 at 23:43 -0700, metronome wrote: > > Thanks for commenting, a few supplements. > > > > # 1. Version of Go? > > We observed the issue with both go1.20.5 and go1.18.10 on linux/amd64 > > (centos) > >

Re: [go-nuts] weird "index out of range" in strconv.formatBits

your guess is more > likely to be true than a random coin flip. > > On Wed, Aug 16, 2023 at 8:31 PM metronome wrote: > >> Hi, >> >> We ran into a weird *out of range* issue of *strconv.formatBits*, hope >> someone can shed a light on what could be the root cau

[go-nuts] weird "index out of range" in strconv.formatBits

Hi, We ran into a weird *out of range* issue of *strconv.formatBits*, hope someone can shed a light on what could be the root cause, any comment is highly appreciated. problem description: * random out of range at code

Re: [go-nuts] epoll: why write 1 byte to the pipe in netpollBreak() and read up to 16 bytes in netpoll()?

Hi Ian, Thanks for clarifying, yes it's no harm to leave the code untouched. On Tuesday, August 15, 2023 at 3:21:57 AM UTC+8 Ian Lance Taylor wrote: > On Mon, Aug 14, 2023 at 11:28 AM metronome wrote: > > > > >> If several different goroutines decide to wake up the pol

Re: [go-nuts] epoll: why write 1 byte to the pipe in netpollBreak() and read up to 16 bytes in netpoll()?

>> If several different goroutines decide to wake up the polling >> goroutine before the polling goroutine wakes up, they will each write >> a single byte Wondering, with the introduction of "netpollWakeSig", does it still hold true? Thanks. On Tuesday, July 11, 2023 at 9:00:36 AM UTC+8 Ian

[go-nuts] about "hybrid barrier"

Hi, I came across two questions regarding the hybrid barrier that I am hoping someone can help with. 1. Chang https://go-review.googlesource.com/c/go/+/31765 says: *"It's unconditional for now because barriers on channel operations require checking both the source and destination stacks

[go-nuts] about "hybrid barrier"

Hi, I came across two questions regarding the hybrid barrier that I am hoping someone can help with. 1. Chang https://go-review.googlesource.com/c/go/+/31765 says: "It's unconditional for now because barriers on channel operations require checking both the source and destination stacks and we