commit 71239b4f491698397149868c88d2c851de2cd49b
author Carlos Eduardo Seo <cseo@linux.vnet.ibm.com> Fri Jan 17 17:59:59 2020 -0300
committer Brad Fitzpatrick <bradfitz@golang.org> Mon Jan 20 15:06:42 2020 +0000
tree 35aacb371529d74c0c19a9f8b57e86b4108d4c4a
parent df2999ef43ea49ce1578137017949c0ee660608a

runtime: fix wrong offset when calling ppc64x nanotime syscall

There is a wrong offset when getting the results of a clock_gettime
syscall. Although the syscall will never be called in native ppc64x,
QEMU doesn't implement VDSO, so it will return wrong values.

Fixes #36592

Change-Id: Icf838075228dcdd62cf2c1279aa983e5993d66ee
Reviewed-on: https://go-review.googlesource.com/c/go/+/215397
Reviewed-by: Tobias Klauser <tobias.klauser@gmail.com>

src/runtime/sys_linux_ppc64x.s

diff --git a/src/runtime/sys_linux_ppc64x.s b/src/runtime/sys_linux_ppc64x.s
index de14418..8629fe3 100644
--- a/src/runtime/sys_linux_ppc64x.s
+++ b/src/runtime/sys_linux_ppc64x.s
@@ -280,7 +280,7 @@
 	ADD	$32, R1, R4
 	SYSCALL $SYS_clock_gettime
 	MOVD	32(R1), R3
-	MOVD	48(R1), R5
+	MOVD	40(R1), R5
 	JMP	finish
 
 TEXT runtime·rtsigprocmask(SB),NOSPLIT|NOFRAME,$0-28