Fix tracing macros for framework builds

Bug: skia:
Change-Id: Ia5c27af2c8dafd5d6f2171fa82f435dbfdebd346
Reviewed-on: https://skia-review.googlesource.com/33760
Reviewed-by: Derek Sollenberger <djsollen@google.com>
Commit-Queue: Brian Osman <brianosman@google.com>
This commit is contained in:
Brian Osman 2017-08-11 13:51:01 -04:00 committed by Skia Commit-Bot
parent 769faa2456
commit 0db0779199

View File

@ -76,9 +76,12 @@ struct SkAndroidFrameworkTraceUtil {
// Records a pair of begin and end events called "name" for the current scope, with 0, 1 or 2
// associated arguments. In the framework, the arguments are ignored.
#define TRACE_EVENT0(category_group, name) SkAndroidFrameworkTraceUtil __trace(name)
#define TRACE_EVENT1(category_group, name, arg1_name, arg1_val) __trace(name)
#define TRACE_EVENT2(category_group, name, arg1_name, arg1_val, arg2_name, arg2_val) __trace(name)
#define TRACE_EVENT0(category_group, name) \
SkAndroidFrameworkTraceUtil __trace(name)
#define TRACE_EVENT1(category_group, name, arg1_name, arg1_val) \
SkAndroidFrameworkTraceUtil __trace(name)
#define TRACE_EVENT2(category_group, name, arg1_name, arg1_val, arg2_name, arg2_val) \
SkAndroidFrameworkTraceUtil __trace(name)
// Records a single event called "name" immediately, with 0, 1 or 2 associated arguments. If the
// category is not enabled, then this does nothing.