Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.
7838 Discussions

OneAPI 2022.3 Compiler crash in Release mode on Windows.

AndrewC
New Contributor III
833 Views

I will supply the files to Intel Support directly if asked.
Oh well, time to downgrade back to 2022.1

>Stack dump:
1>0.	Program arguments: C:\\PROGRA~2\\Intel\\oneAPI\\compiler\\20222~1.0\\windows\\bin-llvm\\clang-cl.exe @C:\\Users\\vaone\\AppData\\Local\\Temp\\273120arg2
1>1.	<eof> parser at end of file
1>2.	Optimizer
1> #0 0x00007ff79eb5c330 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x153c330)
1> #1 0x00007ff79eb9bf10 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x157bf10)
1> #2 0x00007ff79eb76977 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1556977)
1> #3 0x00007ff79eb73a69 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1553a69)
1> #4 0x00007ff79eb61591 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1541591)
1> #5 0x00007ff79df3dbd4 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x91dbd4)
1> #6 0x00007ff79df3dde6 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x91dde6)
1> #7 0x00007ff79fd34ab1 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x2714ab1)
1> #8 0x00007ff79e447a97 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0xe27a97)
1> #9 0x00007ff79ec7f49c (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x165f49c)
1>#10 0x00007ff79ec7421b (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x165421b)
1>#11 0x00007ff79f03eef4 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1a1eef4)
1>#12 0x00007ff7a0529925 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x2f09925)
1>#13 0x00007ff79f038bfb (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1a18bfb)
1>#14 0x00007ff79efae332 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x198e332)
1>#15 0x00007ff79dfdd902 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x9bd902)
1>#16 0x00007ff79e080fc2 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0xa60fc2)
1>#17 0x00007ff79d629444 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x9444)
1>#18 0x00007ff79d625bf3 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x5bf3)
1>#19 0x00007ff79ed65ba6 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x1745ba6)
1>#20 0x00007ff79dbd190f (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x5b190f)
1>#21 0x00007ff79ed652f5 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x17452f5)
1>#22 0x00007ff79df7809e (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x95809e)
1>#23 0x00007ff79df7874d (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x95874d)
1>#24 0x00007ff79df9bd8b (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x97bd8b)
1>#25 0x00007ff79d6243b8 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x43b8)
1>#26 0x00007ff7a179a048 (C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm\clang-cl.exe+0x417a048)
1>#27 0x00007fff53617034 (C:\WINDOWS\System32\KERNEL32.DLL+0x17034)
1>#28 0x00007fff53d426a1 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x526a1)
1>icx: : error : clang frontend command failed due to signal (use -v to see invocation)
1>Intel(R) oneAPI DPC++/C++ Compiler 2022.2.0 (2022.2.0.20220730)
1>Target: x86_64-pc-windows-msvc
1>Thread model: posix
1>InstalledDir: C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin-llvm
1>Configuration file: C:\PROGRA~2\Intel\oneAPI\compiler\20222~1.0\windows\bin\icx.cfg
1>icx: note: diagnostic msg:
1>********************
1>
1>PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:

 

 

0 Kudos
1 Solution
AndrewC
New Contributor III
473 Views

FYI,

 

The latest OneAPI 2023.0 release fixes the bug

 

 

View solution in original post

0 Kudos
6 Replies
HemanthCH_Intel
Moderator
807 Views

Hi,


Thanks for posting in Intel Communities.


Could you please provide the below information to investigate more on your issue:

1)Sample reproducer code and steps to reproduce your issue?

2)OS details and VS version(if you are using Visual Studio).


Thanks & Regards,

Hemanth


0 Kudos
AndrewC
New Contributor III
795 Views

As per my report, I have the files that CLANG dumps that allow the issue to reproduced, that is, the preprocessed .cpp and the .sh file to launch the compiler. I cannot post them publicly. If Intel Support wishes to review the files I can upload them to a secure site.

I am using Visual Studio 2022, Version 17.3.4 on Windows 10/64.

This is not specific to VS 2022 launched builds, as the compiler crash happens when the build is driven by Ninja.


0 Kudos
HemanthCH_Intel
Moderator
702 Views

Hi,


We are working on your issue and will get back to you soon.


Thanks & Regards,

Hemanth


0 Kudos
AndrewC
New Contributor III
594 Views

The latest release of OneAPI (w_BaseKit_p_2022.3.1.19798.exe) still has this optimizer bug and crashes when building this file in release mode

0 Kudos
AndrewC
New Contributor III
474 Views

FYI,

 

The latest OneAPI 2023.0 release fixes the bug

 

 

0 Kudos
SeshaP_Intel
Moderator
460 Views

Hi,


Thanks for the confirmation. Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel


Thanks and Regards,

Pendyala Sesha Srinivas


0 Kudos
Reply