You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/vast/users/abagusetty/compilers/today/llvm/xpti/../xpti/include/xpti/xpti_trace_framework.h:149:11: error: ‘xpti’ does not name a type
149 | virtual xpti::result_t first_item(char **key, xpti::object_id_t &value) = 0;
/vast/users/abagusetty/compilers/today/llvm/xpti/../xpti/include/xpti/xpti_trace_framework.h:1009:23: error: typedef ‘xpti_lookup_string_t’ is initialized (use ‘decltype’ instead)
1009 | typedef const char *(*xpti_lookup_string_t)(xpti::string_id_t);| ^~~~~~~~~~~~~~~~~~~~
/vast/users/abagusetty/compilers/today/llvm/sycl/tools/sycl-trace/ur_trace_collector.cpp:107:1: error: ‘XPTI_CALLBACK_API’ does not name a type; did you mean ‘XPTI_CALLBACK_API_EXPORTS’?
107 | XPTI_CALLBACK_API void urCallback(uint16_t TraceType,
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Faced with build errors from XPTI when building HIP backend for AMD using gcc-13.3.0 and rocm-6.3.0
Configured with:
Some of the build errors are shown below:
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: