-
Notifications
You must be signed in to change notification settings - Fork 18k
time: clean up duplicate definitions time.runtimeTimer
and runtime.timer
that need to be kept in sync
#64549
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
Change https://go.dev/cl/547195 mentions this issue: |
runtimeTimer
is not synced with runtime.timer
time.runtimeTimer
and runtime.timer
that need to be kept in sync
…ntime.timer Fixex golang#64549 Change-Id: Ie6e46309c386e3186396115e20a0ee5b36891db0
Change https://go.dev/cl/559076 mentions this issue: |
See https://go.dev/cl/559076 , merge time.runtimeTimer and runtime.timer to abi.Timer , it's gonna make some weird race. |
…ntime.timer Fixex golang#64549 Change-Id: Ie6e46309c386e3186396115e20a0ee5b36891db0
This is fixed via CL 568339, which removed the duplication. |
Go version
go version go1.21.4 darwin/amd64 and the tip
What operating system and processor architecture are you using (
go env
)?What did you do?
In runtime/time.go:
go/src/runtime/time.go
Lines 16 to 40 in 098f059
The
status
field was changed toatomic.Uint32
, but not synced totime/sleep.go
.go/src/time/sleep.go
Lines 11 to 22 in 098f059
What did you expect to see?
Two structs are synced.
What did you see instead?
They are not.
The text was updated successfully, but these errors were encountered: