aboutsummaryrefslogtreecommitdiff
path: root/design/19348-midstack-inlining.md
diff options
context:
space:
mode:
Diffstat (limited to 'design/19348-midstack-inlining.md')
-rw-r--r--design/19348-midstack-inlining.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/design/19348-midstack-inlining.md b/design/19348-midstack-inlining.md
index b983998..5a86f47 100644
--- a/design/19348-midstack-inlining.md
+++ b/design/19348-midstack-inlining.md
@@ -465,14 +465,14 @@ Prior to this work, Go had the `-l=4` flag to turn on mid-stack inlining,
but this mode had issues beyond incomplete stack traces.
For example, before we could run experiments with `-l=4`, we had to fix
-inlining of variadic functions ([CL 33671](golang.org/cl/33671)),
-mark certain cgo functions as uninlineable ([CL 33722](golang.org/cl/33722)),
-and include linknames in export data ([CL 33911](golang.org/cl/33911)).
+inlining of variadic functions ([CL 33671](https://golang.org/cl/33671)),
+mark certain cgo functions as uninlineable ([CL 33722](https://golang.org/cl/33722)),
+and include linknames in export data ([CL 33911](https://golang.org/cl/33911)).
Before we turn on mid-stack inlining, we will have to update uses
of runtime.Callers in the runtime to use runtime.CallersFrames.
We will also have to make tests independent of inlining
-(e.g., [CL 37237](golang.org/cl/37237)).
+(e.g., [CL 37237](https://golang.org/cl/37237)).
# Preliminary Results