String tracepoint macros

HawkTracer offers multiple macros for measuring time spent in a specific block of code. Each of macros has slightly different behaviour and performance implications. The diagram below can help making the right choice for the macro.

Each of the macros takes a timeline as a parameter (which is a timeline used for posting a tracepoint event to), and optionally, a string label.

There's a few things to keep in mind though:

• For all the macros below, the timeline must have Callstack feature enabled - Global Timeline has this feature enabled by default.
• For all the OPT macros, the timeline must have Cached String feature enabled - Global Timeline has this feature enabled by default.
• If you use Global Timeline, HawkTracer provides simplified macros. The difference between Global Timeline macros is that they don't require the first (timeline) parameter (so, instead of HT_TRACE(ht_global_timeline_get(), "LABEL"), user can just do HT_G_TRACE("LABEL"))
  • HT_TRACE() == HT_G_TRACE()
  • HT_TRACE_FUNCTION(), HT_TRACE_FUNCTION_OPT() == HT_G_TRACE_FUNCTION()
  • HT_TRACE_OPT_DYNAMIC() == HT_G_TRACE_OPT_DYNAMIC()
  • HT_TRACE_OPT_STATIC() == HT_G_TRACE_OPT_STATIC()