aboutsummaryrefslogtreecommitdiff
path: root/src/runtime
diff options
context:
space:
mode:
authorJosh Bleecher Snyder <josharian@gmail.com>2021-10-01 16:19:27 -0700
committerJosh Bleecher Snyder <josharian@gmail.com>2021-10-04 22:27:40 +0000
commit752cc07c77767d28a61525daa359d087b035f5c1 (patch)
tree8e5464f282b8eef1e46c1c36b57483d32bd237db /src/runtime
parent7ee4c1665477c6cf574cb9128deaf9d00906c69f (diff)
downloadgo-752cc07c77767d28a61525daa359d087b035f5c1.tar.xz
cmd, runtime: mark assembly routines in FuncFlags
There's no good way to ascertain at runtime whether a function was implemented in assembly. The existing workaround doesn't play nicely with some upcoming linker changes. This change introduces an explicit marker for routines implemented in assembly. This change doesn't use the new bit anywhere, it only introduces it. Change-Id: I4051dc0afc15b260724a04b9d18aeeb94911bb29 Reviewed-on: https://go-review.googlesource.com/c/go/+/353671 Trust: Josh Bleecher Snyder <josharian@gmail.com> Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Cherry Mui <cherryyz@google.com>
Diffstat (limited to 'src/runtime')
-rw-r--r--src/runtime/symtab.go3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/runtime/symtab.go b/src/runtime/symtab.go
index d1fe1a4fcc..14591602a3 100644
--- a/src/runtime/symtab.go
+++ b/src/runtime/symtab.go
@@ -383,6 +383,9 @@ const (
// to be an incomplete unwinding of the stack. In certain contexts
// (in particular garbage collector stack scans) that is a fatal error.
funcFlag_SPWRITE
+
+ // ASM indicates that a function was implemented in assembly.
+ funcFlag_ASM
)
// pcHeader holds data used by the pclntab lookups.