New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gccgo: etcd reportedly doesn't compile on gccgo #28601
Comments
Change https://golang.org/cl/147537 mentions this issue: |
Change https://golang.org/cl/147442 mentions this issue: |
Updates #28601 Change-Id: I734fc5ded153126d384f0df912ecd4d208005e49 Reviewed-on: https://go-review.googlesource.com/c/147537 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
This is now fixed on GCC 7 branch, GCC 8 branch, and tip. Sorry for the trouble. @glaubitz: Please do report cases where the gc toolchain works and gccgo does not. That's the only way we will know to fix the problems. Thanks. |
Thanks. That was a very quick fix.
This has been on my TODO list forever. I will try to take care of this this week. There are a couple of packages left that have issues. |
Builtin_call_expression::do_numeric_constant_value can be called by Array_type::verify_length before the determine types pass, so accept an abstract type. Test case is https://golang.org/cl/147537. Fixes golang/go#28601 Reviewed-on: https://go-review.googlesource.com/c/147442 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-7-branch@265818 138bc75d-0d04-0410-961f-82ee72b054a4
Builtin_call_expression::do_numeric_constant_value can be called by Array_type::verify_length before the determine types pass, so accept an abstract type. Test case is https://golang.org/cl/147537. Fixes golang/go#28601 Reviewed-on: https://go-review.googlesource.com/c/147442 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-8-branch@265819 138bc75d-0d04-0410-961f-82ee72b054a4
Builtin_call_expression::do_numeric_constant_value can be called by Array_type::verify_length before the determine types pass, so accept an abstract type. Test case is https://golang.org/cl/147537. Fixes golang/go#28601 Reviewed-on: https://go-review.googlesource.com/c/147442 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@265820 138bc75d-0d04-0410-961f-82ee72b054a4
@glaubitz Do you know if they fail with gccgo on amd64 also, or also on PPC64? Is there a way that I could find out? There are of course various possible reasons for this to happen, ranging from a gccgo bug to a non-portable test. I guess we'll just have to examine each one to see what is going on. |
I'll test those packages on amd64. It's actually not that difficult to switch the package over from gc to gccgo. |
@ianlancetaylor Tested all these packages on amd64 with gccgo-8 instead of gc. They all fail the testsuite with gccgo but pass it with gc. |
@glaubitz, feel free to file as many new bugs as you'd like. But reusing this one risks it being ignored, because our dashboard don't track closed issues. |
@glaubitz, feel free to file as many new bugs as you'd like. But reusing this one risks it being ignored, because our dashboard don't track closed issues.
Sure, I‘m aware of that. This was just a quick check and you see there is actually a noticable amount of build issues with gccgo.
I have requested Debian‘s Go packaging team now to fix all their packages which have a hard build dependency to switch that to „golang-any“ such that these packages can attempt to build on the gccgo-only architectures. I expect around 50-60 packages which won’t build with gccgo out that. We‘ll see.
|
We look forward to the reports. When you do report, though, be sure to note exactly what failed: actually building (e.g. compilation failures) vs test failures. The latter is often due to things like tests assuming certain gc-specific behaviors, like naming of symbols in stack frames. In any case, I assume you'll post links to failure logs, so it should be obvious. |
Builtin_call_expression::do_numeric_constant_value can be called by Array_type::verify_length before the determine types pass, so accept an abstract type. Test case is https://golang.org/cl/147537. Fixes golang/go#28601 Reviewed-on: https://go-review.googlesource.com/c/147442 From-SVN: r265819
Pulling this into its own issue from #19074 (comment) where @glaubitz says:
The text was updated successfully, but these errors were encountered: