https://golang.org/cl/246763 made nanotime and walltime reentrant, but on ARM, the calculation of the result used a register expected to be zero which was changed by https://golang.org/cl/246763 to the old value of vdsoSP. This is usually 0, but in a reentrant call would not be, thus generating a bogus result.
The text was updated successfully, but these errors were encountered:
prattmic
added
NeedsFix
The path to resolution is known, but the work has not been done.
arch-arm
Issues solely affecting the 32-bit arm architecture.
labels
Nov 9, 2021
https://golang.org/cl/246763 made nanotime and walltime reentrant, but on ARM, the calculation of the result used a register expected to be zero which was changed by https://golang.org/cl/246763 to the old value of vdsoSP. This is usually 0, but in a reentrant call would not be, thus generating a bogus result.
I already fixed walltime in https://golang.org/cl/361159, but nanotime has a similar issue.
cc @cherrymui
The text was updated successfully, but these errors were encountered: