-
Notifications
You must be signed in to change notification settings - Fork 18k
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
x/tools/gopls: stderr printout in init() from asmdecl analyser #52646
Comments
//cc @findleyr |
I believe this should have been fixed upstream in go/types by https://go.dev/cl/401576. Can you update your Go build to avoid the problem? |
Updating and rebuilding does in fact help, thanks! In our CI we run against Go 1.17 & Go 1.18 so it won't really help us for older versions. I imagine that anything that imports Would it be possible to guard it with a 1.19 build tag as workaround? I'm happy to mail a CL for it. |
@leitzler yes you're right that we should guard the new arch in the asmdecl analyzer with a build tag. If you don't mind mailing a CL, that would be great! Please send to me and @XiaodongLoong |
@leitzler just let us know if you don't think you'll be getting to this. I'd like to fix it before the v0.8.4 release next week. Absolutely no worries if you'd rather we take care of it. |
Change https://go.dev/cl/403874 mentions this issue: |
CC @golang/loong64 |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run
gopls
What did you expect to see?
No printouts to stderr.
What did you see instead?
A printout about
unknown architecture
from theinit()
func in asmdecl analyser introduced via https://go-review.googlesource.com/c/tools/+/356089.This causes problems for govim integration tests as they include explicit checks that there are no stderr printouts.
The text was updated successfully, but these errors were encountered: