-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: GOEXPERIMENT=unified on macOS fails fixedbugs/issue27836.go #53954
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
Comments
I'm going to start bisecting. I tried this on a hunch that something had changed in tip (since the dev.unified branch was working, till the latest merge). |
The I think the bug is here: That suggests https://go.dev/cl/395258 as the culprit (attn @mdempsky). Does March 24 sound like a plausible timeframe? |
It was working on May 2, at the boringcrypto merge 0668e3c . |
So the other half of the problem, no surprise, was |
But package path and package name are separate names. The test is structured so you can vary them independently, and we allow them to vary separately in normal usage too (eg, packages within GOPATH or modules). The problem I think is issue27836 relies on the file system preserving Unicode file names exact byte encoding, but macOS canonicalizes file names in some cases. I would expect the same problem could arise if a Go module had a similarly named directory: it would be compiled as one path on macOS due to canonicalization, and a different one on other OSes. |
Change https://go.dev/cl/418294 mentions this issue: |
Change https://go.dev/cl/418334 mentions this issue: |
…s not translated by macOS. In filenames, macOS translates Ä (U+00c4, c3 84) to Ä (U+0041 U+0308, 41 cc 88). This causes problems for run.go's crude rules for testing the compiler. Fixes golang#53954. Change-Id: I850421cbf07e022ca5ff8122e0fb4e80deb55adf Reviewed-on: https://go-review.googlesource.com/c/go/+/418334 Run-TryBot: David Chase <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Matthew Dempsky <[email protected]>
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?
What did you expect to see?
Success
What did you see instead?
The text was updated successfully, but these errors were encountered: