Re: [go-nuts] How to test the 'noasm' code?

On Tue, Apr 25, 2023 at 10:57 AM Sam Vilain wrote: > > (a) where can I find how this specific optimization is defined? It's in the compiler. It's not especially easy to pull it out. In this specific case, it's something like cmd/compile/internal/ssagen/ssa.go: addF("math/bits", "TrailingZ

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

Please do not install Docker as a snap, as this fundamentally breaks several parts of Docker. This is a well known limitation of snap. Simply install from the Docker repository, instructions are on the Docker website. Building Docker is complicated, as it predates Go modules and still has no fu

Re: [go-nuts] How to test the 'noasm' code?

Oh, man. I was wondering why, when I built my assembly version; // Counts trailing Zero bits TEXT ·Ctz(SB),NOSPLIT,$0-1 MOVQ val+0(FP), AX // value to be counted TZCNTQ AX, BX MOVB BX, ret+8(FP) RET I got this: $ go build -o hybrid8b.o . $ go tool objdump -s hybrid8b.Ctz hybri

Re: [go-nuts] How to test the 'noasm' code?

On Tue, Apr 25, 2023 at 10:03 AM Sam Vilain wrote: > > Looks like `math/bits` could use some assembly alternatives, too. Clever as > those functions are, they're almost certainly not going to beat the > microcode/silicon. I'm looking into the contribution guidelines now! Note that many of the

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

Like I said, those instructions are woefully out of date. Whilst the Go language has a compatibility guarantee for code written in Go, this does not apply to the tooling, which is subject to change over time. One of the major changes was the introduction of Go modules

Re: [go-nuts] How to test the 'noasm' code?

Aha, thanks! And there -tags is, on `go help build`. I wasn't sure what 'noasm' was; I was copying from an example by searching my ~/go/pkg; in this case the 'snappy' source (github.com/golang/snappy). I had assumed it was something that gets set automatically, if for whatever reason assembly

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

No, like "go doc --help" instead of "godoc --help" On Tuesday, 25 April 2023 at 17:21:27 UTC+1 Mario Marietto wrote: > like this ? > > $ go get golang.org/x/tools/cmd/go doc > > go: module golang.org/x/tools@upgrade found (v0.8.0), but does not > contain package golang.org/x/tools/cmd/go > go:

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

like this ? $ go get golang.org/x/tools/cmd/go doc go: module golang.org/x/tools@upgrade found (v0.8.0), but does not contain package golang.org/x/tools/cmd/go go: malformed module path "doc": missing dot in first path element On Tue, Apr 25, 2023 at 6:16 PM Brian Candler wrote: > You're fol

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

You're following out-of-date instructions. godoc is now "go doc". On Tuesday, 25 April 2023 at 16:52:09 UTC+1 Mario Marietto wrote: > Hello to everyone. > > I've restarted the tutorial from the beginning and I've saved every > command issued : > > $ cd /home/marietto > $ wget https://dl.google.c

Re: [go-nuts] How to test the 'noasm' code?

On Tue, Apr 25, 2023 at 8:38 AM Sam Vilain wrote: > > I have a module that has a couple of assembly functions (for CLZ aka > BSR/LZCNT, which despite widespread availability[1] don't get any language > support). So I've got the assembly versions in per–arch files, and a "noasm" > version that

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

Hello to everyone. I've restarted the tutorial from the beginning and I've saved every command issued : $ cd /home/marietto $ wget https://dl.google.com/go/go1.20.3.linux-arm64.tar.gz $ tar -xf archive.tar.gz $ mv go go1.20.3 $ nano /home/marietto/.profile PATH="$HOME/bin:$HOME/.local/bin:$PATH

[go-nuts] How to test the 'noasm' code?

I have a module that has a couple of assembly functions (for CLZ aka BSR/LZCNT, which despite widespread availability[1] don't get any language support). So I've got the assembly versions in per–arch files, and a "noasm" version that builds with "noasm" (amongst other typical conditions. My qu

Re: [go-nuts] FATAL: ThreadSanitizer: unsupported VMA range FATAL: Found 39 - Supported 48 / go: added github.com/docker/docker v23.0.4+incompatible

Hello to everyone. I've restarted the tutorial from the beginning and I'm trying to accomplish the next step,as indicated where he says : "*Note* containerd by default installs as static in the install script. Due to that failing (most likely needs musl to properly compile statically) I instead d