Go 1.7 Release Candidate 6 is released
3,609 views
Skip to first unread message
Chris Broadfoot
Aug 8, 2016, 4:44:40 PM8/8/16
to golang-nuts
Hello gophers,
We have just released go1.7rc6, a release candidate for Go 1.7.
Some say that it's the best one yet.
It is cut from release-branch.go1.7 at the revision tagged go1.7rc6.
Please help us by testing your Go programs with the release, and
report any problems using the issue tracker:
You can download binary and source distributions from the usual place:
To find out what has changed in Go 1.7, read the draft release notes:
Documentation for Go 1.7 is available at:
A comprehensive list of changes since rc5 is here:
We plan to issue Go 1.7 in a week's time (August 15).
Cheers,
Chris
David Marceau
Aug 10, 2016, 10:00:37 AM8/10/16
to golang-nuts
when I install from sources straight from git checkout go1.7rc6
go1.7rc6 FAILS on Asus Z97-A-USB31 motherboard with intel i5-4590,
"../misc/cgo/testsanitizers"
it core dumps and doesn't give me the success message to start using it as the previous go1.7rc[1-4] did.
signal: segmentation fault (core dumped)
FAIL: msan
FAIL: msan2
FAIL: msan3
FAIL: msan4
... FAILED
To contrast this, Go1.7rc6 does succeed on another much older motherboard Dell Inc. Vostro 430/054KM3, BIOS 2.2.0.
go1.7rc6 FAILS on Asus Z97-A-USB31 motherboard with intel i5-4590,
"../misc/cgo/testsanitizers"
it core dumps and doesn't give me the success message to start using it as the previous go1.7rc[1-4] did.
signal: segmentation fault (core dumped)
FAIL: msan
FAIL: msan2
FAIL: msan3
FAIL: msan4
... FAILED
To contrast this, Go1.7rc6 does succeed on another much older motherboard Dell Inc. Vostro 430/054KM3, BIOS 2.2.0.
David Marceau
Aug 11, 2016, 12:07:01 PM8/11/16
to golang-nuts
Ok so yes I recently installed clang on this archlinux box. The previous go binaries were built with gcc/g++.
So to clarify and save others time:
1)to build using gcc/g++:
CC=/usr/bin/gcc CXX=/usr/bin/g++ GOROOT_BOOTSTRAP=/root/go1.7rc5 ./make.bash
2)to build using clang/clang++:
CC=/usr/bin/clang CXX=/usr/bin/clang++ GOROOT_BOOTSTRAP=/root/go1.7rc5 ./make.bash
By explicitly setting those CC and CXX variables, I was able to revert to my original gcc/g++ built golang binaries in order to be consistent since my earlier binaries were built with gcc/g++ I prefer to stay on that path for the moment.
So to clarify and save others time:
1)to build using gcc/g++:
CC=/usr/bin/gcc CXX=/usr/bin/g++ GOROOT_BOOTSTRAP=/root/go1.7rc5 ./make.bash
2)to build using clang/clang++:
CC=/usr/bin/clang CXX=/usr/bin/clang++ GOROOT_BOOTSTRAP=/root/go1.7rc5 ./make.bash
By explicitly setting those CC and CXX variables, I was able to revert to my original gcc/g++ built golang binaries in order to be consistent since my earlier binaries were built with gcc/g++ I prefer to stay on that path for the moment.
foo bar
Aug 11, 2016, 7:44:29 PM8/11/16
to golang-nuts
Hi David,
The issue you are having seems related to https://github.com/golang/go/issues/16636
I'm also running Arch Linux, and it seems like
The issue you are having seems related to https://github.com/golang/go/issues/16636
I'm also running Arch Linux, and it seems like
-fsanitize=memory is broken on general for Clang on Arch. Would you be able to verify if this is also the case for you? Add a comment to the issue, rather than this thread to keep the discussion on track.
Cheers /u
decr...@gmail.com
Sep 7, 2016, 11:21:46 AM9/7/16
to golang-nuts
понедельник, 8 августа 2016 г., 23:44:40 UTC+3 пользователь Chris Broadfoot написал:
Reply all
Reply to author
Forward
0 new messages