From a83748596c009db47bcd35a69531e485e2c7f924 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Wed, 17 Jul 2013 12:47:18 -0400 Subject: runtime: use new frame argument size information With this CL, I believe the runtime always knows the frame size during the gc walk. There is no fallback to "assume entire stack frame of caller" anymore. R=golang-dev, khr, cshapiro, dvyukov CC=golang-dev https://golang.org/cl/11374044 --- src/pkg/runtime/softfloat_arm.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'src/pkg/runtime/softfloat_arm.c') diff --git a/src/pkg/runtime/softfloat_arm.c b/src/pkg/runtime/softfloat_arm.c index 9a54406302..56a73fce5c 100644 --- a/src/pkg/runtime/softfloat_arm.c +++ b/src/pkg/runtime/softfloat_arm.c @@ -576,9 +576,12 @@ done: return 0; } +// The ... here is because there are actually 16 registers +// being passed (r0, r1, and so on) amd we are too lazy +// to list them all. #pragma textflag 7 uint32* -runtime·_sfloat2(uint32 *lr, uint32 r0) +runtime·_sfloat2(uint32 *lr, uint32 r0, ...) { uint32 skip; -- cgit v1.3-5-g9baa