diff options
| author | Ian Lance Taylor <ian@gcc.gnu.org> | 2019-06-03 23:07:54 +0000 |
|---|---|---|
| committer | Ian Lance Taylor <ian@gcc.gnu.org> | 2019-06-03 23:07:54 +0000 |
| commit | c533ffe04d5fc1baa85dddd8fd5f651128cf11ed (patch) | |
| tree | 9b0df7f8a2130484fd7458745c8ec0361f3f9850 /gcc | |
| parent | 3e6f8fe1bc4c60859113bca7970b0b8db56eb442 (diff) | |
| download | gcc-c533ffe04d5fc1baa85dddd8fd5f651128cf11ed.zip gcc-c533ffe04d5fc1baa85dddd8fd5f651128cf11ed.tar.gz gcc-c533ffe04d5fc1baa85dddd8fd5f651128cf11ed.tar.bz2 | |
libgo: delay applying profile stack-frame skip until fixup
When the runtime collects a stack trace to associate it with some
profiling event (mem alloc, mutex, etc) there is a skip count passed
to runtime.Callers (or equivalent) to skip some known count of frames
in order to get to the "interesting" frame corresponding to the
profile event. Now that the profiling mechanism uses lazy fixup (when
removing compiler artifacts like thunks, morestack calls etc), we also
need to move the frame skipping logic after the fixup, so as to insure
that the skip count isn't thrown off by these artifacts.
Fixes golang/go#32290.
Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/179740
From-SVN: r271892
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/go/gofrontend/MERGE | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gcc/go/gofrontend/MERGE b/gcc/go/gofrontend/MERGE index 43df2f7..1b2fd70 100644 --- a/gcc/go/gofrontend/MERGE +++ b/gcc/go/gofrontend/MERGE @@ -1,4 +1,4 @@ -37a47e4691b4602dd167f82c64a6569019584a80 +951c83af46375019b2fe262635746368a6b9c4ba The first line of this file holds the git revision number of the last merge done from the gofrontend repository. |