use gcc-go instead of go #73

New Issue

Open

opened 2021-12-02 11:06:54 +01:00 by Gontier-Julien · 2 comments

Gontier-Julien commented

2021-12-02 11:06:54 +01:00

As the arch wiki for go said, gcc-go might offer better optimizations, and on some of my testing less build time.

The standard Go compiler is go, which can be installed from the go package. [...] An alternative is gcc-go, which is a Go frontend for the GNU Compiler Collection (GCC). In some cases gccgo may do better optimisations. When in doubt: use go.

As the [arch wiki for go](https://wiki.archlinux.org/title/Go#Installation) said, gcc-go might offer better optimizations, and on some of my testing less build time. > The standard Go compiler is go, which can be installed from the go package. [...] An alternative is gcc-go, which is a Go frontend for the GNU Compiler Collection (GCC). In some cases gccgo may do better optimisations. When in doubt: use go.

anonfunc added the

enhancement

label 2021-12-02 11:13:08 +01:00

anonfunc commented

2021-12-02 12:09:09 +01:00

Owner

I did some research on this. gcc-go is certainly the better option overall, but one of its major downsides is that it falls behind in what go-version it supports quite quickly because it's dependent on the gcc release cycle.

That aside, we would need some testing if a 'simple' replace of the go build would be enough to build with gcc-go or not.

I did some research on this. `gcc-go` is certainly the better option overall, but one of its major downsides is that it falls behind in what go-version it supports quite quickly because it's dependent on the gcc release cycle. That aside, we would need some testing if a 'simple' replace of the `go build` would be enough to build with `gcc-go` or not.

👍 1

anonfunc changed title from ~~[Suggestion] use gcc-go instead of go~~ to use gcc-go instead of go

2021-12-31 12:15:00 +01:00

RubenKelevra commented

2022-05-05 19:04:40 +02:00

Contributor

@anonfunc Go programs usually specifify the minimum go version they need. So if the program is specifing something below the go version gcc-go can provide we could try to build it with gcc-go. If it's successfull we could offer the package, if not just retry on the next version.

I think eventually most programs will support both. :)