On Thursday 06 October 2011 10:14:06 Graham Anderson wrote:

Sascha, List

The go release 59 package in factory has some issues, the binaries compiled from Go sources are problematic, godoc, goinstall, gofmt, gofix at least segfault for me on 12.1 beta 1.

Sascha, the compiler/linker (written in C) etc seem unaffected so I'm wondering if stripping the go binaries was (re)enabled in that package revision? Uhm, quite possible as I experimented a bit. Upstream implied that the ELF- related issues where fixed, but they are not (yet).

Anyhow, the release 60 release in devel:languages:go seems fine. Just building a package for yesterdays 60.2 micro release... I've made a couple of tweaks to the package and a minor patch to the linker to allow gdb to use go specific pretty printer and helper functions. Sascha would you please review it when i submitreq it to D:L:Go? I'll start fixing up the other lib packages that need updated against r60. Sure, feel free to submit to Factory, too. The faster the better.

This got me thinking, binaries and libraries built from the gccgo implementation should have native support in gdb, but I don't see a GCC front end for Go, now that we are on GCC 4.6 do we build this at all? It is currently disabled, AFAIR you'll get linking issues when using both GCC and 6g/8g object code.

The gccgo implementation seems to be in reasonably good shape these days and; as far as I know, while still a bit slower to compile than the Plan 9 style compilers, it does produce faster code. I'd like to see us have the gccgo frontend for go as well as the native implementation, is this something the GCC maintainers would consider or should I take this on myself? Short answer: yes! -- Viele Grüße, Sascha