Detecting underfined behavior with ICPX

peizhao — Tue, 09 Jan 2024 18:09:38 GMT

I've encountered undefined behavior in my SYCL application, leading to incorrect results when compiled with the -O2 option. I attempted to detect this using a sanitizer, configuring my CMake file with compile options like:

add_compile_options(-Wall -g -O2 -fsanitize=undefined)

set(SYCL_FLAGS "-fsycl"

"-fsycl-targets=spir64_x86_64"

"-fsycl-unnamed-lambda"

"-Wno-linker-warnings")

.......

target_link_libraries(-fsanitize=undefined)

However, during the build stage, I received a warning icpx: warning: ignoring '-fsanitize=undefined' option as it is not currently supported for target 'spir64_x86_64-unknown-unknown' [-Woption-ignored].

How can I enable a sanitizer with ICPX for my 12th Gen Intel® Core™ i9-12900H CPU?

Re: Detecting underfined behavior with ICPX

Alex_Y_Intel — Fri, 05 Apr 2024 22:25:27 GMT

-fsanitize=undefined and -fsycl-targets=spir64_x86_64 options cannot be used together. you may want to take off -fsycl-targets=spir64_x86_64, depending on what you want to achieve.

topic Detecting underfined behavior with ICPX in Intel® oneAPI DPC++/C++ Compiler

Detecting underfined behavior with ICPX

Re: Detecting underfined behavior with ICPX