Open krasznaa opened 8 months ago
PLEASE append the compiler options "-save-temps -v", rebuild the application to to get the full command which is failing and submit a bug report to https://software.intel.com/en-us/support/priority-support which includes the failing command, input files for the command and the crash backtrace (if any).
@krasznaa, I would recommend using intel forum to report bugs which can be reproduced with the open source version of DPC++ compiler. NOTE: This repository doesn't have icpx
driver, so we can't address it here.
Intel Forums are monitored by a dedicated support team, which will help with reporting the bug to the right team.
Hi Alexey,
I tried. For the Nth time already. But that link just takes me to "priority support". Which I don't currently have. Which makes me always very surprised that apparently only paying customers are encouraged to open bug reports.
To clarify, by "Intel forum" did you mean https://community.intel.com? Unfortunately with a quick look on https://community.intel.com/t5/Intel-C-Compiler/bd-p/c-compiler I only see the "simple support questions" getting much attention. The more technical threads seem to be all unanswered. :frowning:
Let me tag @ivorobts here. Once he comes back from his holidays, hopefully he'll be able to advise on how I should best report such issues in the future... :thinking:
Best, Attila
Hi @bader @krasznaa, as a support engineer, I will create a ticket and we will continue working via email \ support portal.
@ashadrina, thank you!
Describe the bug
While compiling a specific source file, I made
icpx
(from oneAPI 2024.0.1) crash. Usingclang++
from the same oneAPI installation instead, allowed the compilation to succeed. :thinking:The project producing the issue is: https://github.com/acts-project/detray
The issue happens while building this source file: https://github.com/acts-project/detray/blob/main/tests/benchmarks/cuda/benchmark_propagator_cuda.cpp
While it is a "CUDA related" file in our project, it doesn't even include any of the CUDA headers itself. :thinking: The crash produced the following output:
To reproduce
I've put the two files generated by the above described crash, here:
Environment
Additional context
At first I thought that this may be related to #13010, but it's probably not. :thinking: Hence the separate issue.