Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(348)

Unified Diff: build/common.gypi

Issue 17115015: Add 'profiling_full_stack_frames' build option not to optimize out stack frames when profiling. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: rebased Created 7 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index bb9f78142faecb0b78c756ba7949adac7fb01d29..61f6630903c10190beed0c95b7c71cfe1ffc5b9f 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -962,6 +962,8 @@
# Enable sampling based profiler.
# See http://google-perftools.googlecode.com/svn/trunk/doc/cpuprofile.html
'profiling%': '0',
+ # Profile without optimizing out stack frames when profiling==1.
+ 'profiling_full_stack_frames%': '0',
# Enable strict glibc debug mode.
'glibcxx_debug%': 0,
@@ -2833,6 +2835,14 @@
'-fno-omit-frame-pointer',
'-g',
],
+ 'conditions' : [
+ ['profiling_full_stack_frames==1', {
+ 'cflags': [
+ '-fno-inline',
+ '-fno-optimize-sibling-calls',
+ ],
+ }],
+ ],
}],
# Can be omitted to reduce output size. Does not seem to affect
# crash reporting.
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698