New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support JIT-Profiling API #76
Comments
hfp
added a commit
that referenced
this issue
May 6, 2016
…ronment (or allow to manually specify VTUNEROOT), and setup the build environment (include directory, and linking against libjitprofiling). Include jitprofiling.h when LIBXSMM_VTUNE is defined.
hfp
added a commit
that referenced
this issue
May 6, 2016
* Turned tabs into white spaces in any location which is not a rule (Makefile*) * Link against JIT profiling library at LIBXSMM level (unpacking libjitprofiling.a, etc.) * Trigger profiling event iJVM_EVENT_TYPE_METHOD_LOAD_FINISHED
hfp
added a commit
that referenced
this issue
May 7, 2016
* Moved JIT profiling rule up in order to hit earlier rules wrt DFLAGS/IFLAGS (Makefile). * Refactored code into internal_get_code_name and internal_get_vtune_jitdesc * Unregister JIT code from profiling engine (during libxsmm_finalize)
Implemented and validated for the master version. |
hfp
added a commit
that referenced
this issue
May 13, 2016
…ure to supply the name of the JIT engine (module name of the JIT'ted code). Fixed NULL-pointer access in finalization stage. [skip ci]
hfp
added a commit
that referenced
this issue
May 13, 2016
hfp
added a commit
that referenced
this issue
May 14, 2016
… fit with the case that the library is built as a shared object ("LIBXSMM" -> "libxsmm.jit"). [skip ci]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support the JIT-profiling API (Intel VTune Amplifier) when symbols are included (SYM=1 or DBG=1).
The text was updated successfully, but these errors were encountered: