-
Notifications
You must be signed in to change notification settings - Fork 18k
gccgo: reflection-based type printing inconsistency #23620
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
Labels
Milestone
Comments
Change https://golang.org/cl/91138 mentions this issue: |
Change https://golang.org/cl/91139 mentions this issue: |
Thank you @tamird for this bug report. |
hubot
pushed a commit
to gcc-mirror/gcc
that referenced
this issue
Feb 1, 2018
This matches the gc compiler. The test case was sent for the master repo as https://golang.org/cl/91138. Fixes golang/go#23620 Reviewed-on: https://go-review.googlesource.com/91139 git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@257300 138bc75d-0d04-0410-961f-82ee72b054a4
gopherbot
pushed a commit
that referenced
this issue
Feb 14, 2018
Gccgo failed this test. Updates #23620 Change-Id: I3979a6d3b87d2d014850accf9cb7f356349e6195 Reviewed-on: https://go-review.googlesource.com/91138 Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Than McIntosh <[email protected]>
asiekierka
pushed a commit
to WonderfulToolchain/gcc-ia16
that referenced
this issue
May 16, 2022
This matches the gc compiler. The test case was sent for the master repo as https://golang.org/cl/91138. Fixes golang/go#23620 Reviewed-on: https://go-review.googlesource.com/91139 From-SVN: r257300
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version
)?go version go1.10beta2 gccgo (GCC) 8.0.1 20180126 (experimental) linux/amd64
Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (
go env
)?What did you do?
https://play.golang.org/p/HRkuS74EjTu
What did you expect to see?
struct { error }
What did you see instead?
struct { ? error }
The text was updated successfully, but these errors were encountered: