oneapi-src / oneapi-src/unified-runtime
RelWithDebInfo builds fail on Windows
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Description
@sommerlukas reported that building DPC++ on Windows with a RelWithDebInfo config fails with errors relating to XPTI:
_deps\unified-runtime-src\source\loader\layers\tracing\ur_tracing_layer.cpp(15): fatal error C1083: Cannot open include file: 'xpti/xpti_data_types.h': No such file or directory
He was able to resolve this with an older build but found another issue with unresolved symbols:
__imp__invalid_parameter
__imp__CrtDbgReport
And also mismatches with _ITERATOR_DEBUG_LEVEL and RuntimeLibrary
_ITERATOR_DEBUG_LEVEL is possibly due to linking the wrong lib C - @kbenzie
This is something that should be investigated, it is noted that normal Debug and Release builds do work successfully.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows RelWithDebInfo build and inspect the reported unified-runtime-src/source/loader/layers/tracing/ur_tracing_layer.cpp include failure. Compare the working Debug and Release configurations with RelWithDebInfo, then verify that the build completes without the XPTI missing-header error, unresolved symbols, or _ITERATOR_DEBUG_LEVEL and RuntimeLibrary mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100