<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re:OpenMP Segmentation Fault on XE Max GPU in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269502#M8009</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for reaching out to us.&lt;/P&gt;&lt;P&gt;We can see that you have posted the same thread on&amp;nbsp;the Intel oneAPI HPC Toolkit forum, so will no longer monitor this thread as it's a duplicate.&lt;/P&gt;&lt;P&gt;Please expect the reply on the other thread, link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.intel.com/t5/Intel-oneAPI-HPC-Toolkit/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269309#M8002" target="_blank"&gt;https://community.intel.com/t5/Intel-oneAPI-HPC-Toolkit/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269309#M8002&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Warm REgards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 31 Mar 2021 07:03:29 GMT</pubDate>
    <dc:creator>AbhishekD_Intel</dc:creator>
    <dc:date>2021-03-31T07:03:29Z</dc:date>
    <item>
      <title>OpenMP Segmentation Fault on XE Max GPU</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269373#M8005</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I am trying to find the cause of a segmentation fault when running several of the SPEC Accel OpenMP benchmarks. Specifically, I have been working with the 552.ep (embarrassingly parallel) benchmark.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;OS: x86_64 GNU/Linux&lt;BR /&gt;CPU: Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz&lt;BR /&gt;Accelerator: Intel Iris Xe MAX&lt;BR /&gt;Toolkit: Intel(R) oneAPI DPC++ Compiler 2021.1.2 (2020.10.0.1214)&lt;/P&gt;
&lt;P&gt;Compilation commands:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;$ ulimit -s unlimited
$ export IGC_EnableDPEmulation=1
$ export OverrideDefaultFP64Settings=1
$ source /opt/intel/oneapi/setvars.sh

$ icx -g -Wall -O3 -I. -fiopenmp -fopenmp-targets=spir64 *.c -o ep -lm
$ gdb ./ep&lt;/LI-CODE&gt;
&lt;P&gt;&lt;SPAN&gt;Here is the result of running gdb (run). I can install the missing debuginfos and update the question if that would help in finding a solution. I can include the backtrace (gdb bt) also if that would&amp;nbsp;be helpful.&lt;/SPAN&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;(gdb) run
Starting program: /552.pep/src/ep 
Missing separate debuginfos, use: yum debuginfo-install glibc-2.28-127.el8.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
[New Thread 0x155550008700 (LWP 811436)]
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
[New Thread 0x15554d9ac700 (LWP 811437)]
 Reading from input file ep.input


 NAS Parallel Benchmarks (NPB3.3-OPENMP-C) - EP Benchmark

 Number of random numbers generated:        67108864

Thread 1 "ep" received signal SIGSEGV, Segmentation fault.
0x000015553f455bca in vISA::G4_SrcRegRegion::computeLeftBound() () from /lib64/libigc.so.1
Missing separate debuginfos, use: yum debuginfo-install ...&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, I'm intending to use the level0 backend, but I see "OpenCLProgramContext" in the gdb output. Does this mean I may be using the OpenCL backend by mistake?&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 21:13:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269373#M8005</guid>
      <dc:creator>lamb</dc:creator>
      <dc:date>2021-03-30T21:13:58Z</dc:date>
    </item>
    <item>
      <title>Re:OpenMP Segmentation Fault on XE Max GPU</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269502#M8009</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks for reaching out to us.&lt;/P&gt;&lt;P&gt;We can see that you have posted the same thread on&amp;nbsp;the Intel oneAPI HPC Toolkit forum, so will no longer monitor this thread as it's a duplicate.&lt;/P&gt;&lt;P&gt;Please expect the reply on the other thread, link:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.intel.com/t5/Intel-oneAPI-HPC-Toolkit/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269309#M8002" target="_blank"&gt;https://community.intel.com/t5/Intel-oneAPI-HPC-Toolkit/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269309#M8002&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Warm REgards,&lt;/P&gt;&lt;P&gt;Abhishek&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Mar 2021 07:03:29 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/OpenMP-Segmentation-Fault-on-XE-Max-GPU/m-p/1269502#M8009</guid>
      <dc:creator>AbhishekD_Intel</dc:creator>
      <dc:date>2021-03-31T07:03:29Z</dc:date>
    </item>
  </channel>
</rss>

