go
go copied to clipboard
4ad
Go development tree for the sparc64 port
Hi! I'm opening this issue to be able to track the efforts for porting Go to Linux/sparc64. For the porting work, I suggest using Debian unstable for sparc64 rather than...
Please do not send pull requests to the golang/* repositories. We do, however, take contributions gladly. See https://golang.org/doc/contribute.html Thanks!
1. What version of Go are you using (`go version`)? ```bash toomasp@tar1312d1:/opt/local/tmp/go/src$ GOROOT=$GOROOT_BOOTSTRAP $GOROOT_BOOTSTRAP/bin/go version go version devel +69a12818b6 Mon Dec 19 10:29:52 2016 -0800 solaris/sparc64 ``` 2. What operating...
This fixes bugs that show up when dwarf from Studio compilers gets mixed in via crt files.
``` # go run run.go -- fixedbugs/issue13160.go exit status 1 panic: bad pointer read 0xc2f8! goroutine 20 [running]: panic(0x12d380, 0xc42000c300) /builds/srwalker/golang/go-sparc/src/runtime/panic.go:507 +0x5f8 main.main.func2(0xc420016180, 0x8, 0x8, 0x7, 0xc420016140, 0x8, 0x8, 0xc42005c060)...
### Executive Summary: Problem exists in all versions of golang that I checked up to 1.8.3, but it's related to Solaris support, so I'm filing the issue here. I found...
Aram's notes: - Things are saved on the stack in different places comapred to other architectures, even accounting for the stack bias. plus there is the whole register windows spill...
Even on x86, Go's internal linker does not write .dynsym / .symtab entries as expected. In particular, functions imported from libraries such as libc.so (e.g. via loadcgo) when written to...
Originally the code used short or long prologs depending on necessity. This worked, but one of either mdb(1) or DTrace couldn't produce stack traces with short prologs (can't remember which),...