allow bit masking to select various trace features.
bit 0 => Launch tracing (stderr)
bit 1 => timing of runtime (stdout)
bit 2 => detailed launch tracing (stderr)
bit 3 => timing goes to stdout instead of stderr
example: LIBOMPTARGET_KERNEL_TRACE=7 does it all
LIBOMPTARGET_KERNEL_TRACE=5 Launch + details
LIBOMPTARGET_KERNEL_TRACE=2 timings + launch to stderr
LIBOMPTARGET_KERNEL_TRACE=10 timings + launch to stdoutDetails
Diff Detail
Event Timeline
Not Johannes, but probably yes. Wonder if we're missing the license header on other files in this plugin.
The int print_kernel_trace is a wide contract - it suggests it might be toggled from anywhere. Which it isn't. We should change to something more like the other debug/env wrapper and use a function call to access. Independent of this review - just reminded of it by seeing the raw int declaration.
clang-tidy: warning: header guard does not follow preferred style [llvm-header-guard]
not useful