October 2019 - Ecp-aurora-sdk-discuss

Iris queues
by Kumaran, Kalyan 25 Oct '19

25 Oct '19

We have a new queue 'iris_debug' which has a 45 max wall-time and had been assigned to iris[00-03]. The existing iris queue max wall-time has been increased to 6 hours. -Kumar

1 0

Re: [Ecp-aurora-sdk-discuss] Issues building example codes with A21 SDK version 2019.9.30.013
by Knepper, Sarah 24 Oct '19

24 Oct '19

Greetings, Thank you for trying out the new SDK! I noticed that the mkl module file for the latest SDK sets the SDK_DIR to the "intel_dga" directory instead of the "CNDA" directory. As a workaround, after loading the mkl module, you can set the MKLROOT to the accessible directory: export MKLROOT=/soft/restricted/CNDA/sdk/2019.9.30.013/mkl/latest/ Though some of the other environment variables may need to be adjusted as well. After doing this, you should no longer get the fatal error 'mkl_blas_sycl.hpp' file not found. That said, there are some incompatible changes that have been made between the SDK used in the workshop and the latest SDK. For instance, there is now a blas namespace, so the gemm functionality is now located at mkl::blas::gemm. So the example codes from the Aurora Programming Workshop may not work with the new 2019.9.30.013 version of the A21 SDK. However, please find examples provided as part of the new SDK in: /soft/restricted/CNDA/sdk/2019.9.30.013/mkl/latest/examples/. You may be most interested in the examples_sycl.tgz archive. Thanks, Sarah From: Ecp-aurora-sdk-discuss [mailto:[email protected]] On Behalf Of Nicholas Chaimov via Ecp-aurora-sdk-discuss Sent: Thursday, October 24, 2019 3:00 PM To: ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov Subject: [Ecp-aurora-sdk-discuss] Issues building example codes with A21 SDK version 2019.9.30.013 Hello, I was trying to use the example codes from the Aurora Programming Workshop with the new version of the A21 SDK, 2019.9.30.013, but am having problems building several of them. To build the MKL examples in /soft/restricted/CNDA/apps/2019_aurora_workshop/sdk_samples/mkl, I am following the instructions in the slides provided at the workshop. It works if I load the older 2019.6.30.011 modules, but with 2019.9.30.013 I get: [nchaimov1@jlselogin1 mkl]$ clang++ -fsycl -I${MKLROOT}/include -Icommon -DMKL_ILP64 -w -DSYCL_DEVICES_all -c blas/gemm_example.cpp "" -o gemm_example.o blas/gemm_example.cpp:47:10: fatal error: 'mkl_blas_sycl.hpp' file not found #include "mkl_blas_sycl.hpp" ^~~~~~~~~~~~~~~~~~~ 1 error generated. blas/gemm_example.cpp:47:10: fatal error: 'mkl_blas_sycl.hpp' file not found #include "mkl_blas_sycl.hpp" ^~~~~~~~~~~~~~~~~~~ 1 error generated. Also, with the SYCL examples at https://github.com/kevin-harms/sycltrain/tree/master/9_sycl_of_hell, they build correctly with the dpcpp/2019.6.30.011 module, but with dpcpp/2019.9.30.013 I get: clang++ -o 5_buffer_slm 5_buffer_slm.cpp -std=c++17 -fsycl -lOpenCL 5_buffer_slm.cpp:34:7: error: SYCL kernel cannot call a variadic function printf( "slm rank: %d \n", slm[world_rank % INT_MAX ]); ^ 1 error generated. Are there changes to the codes and/or to the build process needed for these to work with the new SDK? Thanks for your help, Nicholas Chaimov HPC Computer Scientist ParaTools, Inc. 1900 Millrace Drive, Box 1, Suite 104 Eugene, OR 97403 (503) 869-8513

1 0

Issues building example codes with A21 SDK version 2019.9.30.013
by Nicholas Chaimov 24 Oct '19

24 Oct '19

Hello, I was trying to use the example codes from the Aurora Programming Workshop with the new version of the A21 SDK, 2019.9.30.013, but am having problems building several of them. To build the MKL examples in /soft/restricted/CNDA/apps/2019_aurora_workshop/sdk_samples/mkl, I am following the instructions in the slides provided at the workshop. It works if I load the older 2019.6.30.011 modules, but with 2019.9.30.013 I get: [nchaimov1@jlselogin1 mkl]$ clang++ -fsycl -I${MKLROOT}/include -Icommon -DMKL_ILP64 -w -DSYCL_DEVICES_all -c blas/gemm_example.cpp "" -o gemm_example.o blas/gemm_example.cpp:47:10: fatal error: 'mkl_blas_sycl.hpp' file not found #include "mkl_blas_sycl.hpp" ^~~~~~~~~~~~~~~~~~~ 1 error generated. blas/gemm_example.cpp:47:10: fatal error: 'mkl_blas_sycl.hpp' file not found #include "mkl_blas_sycl.hpp" ^~~~~~~~~~~~~~~~~~~ 1 error generated. Also, with the SYCL examples at https://github.com/kevin-harms/sycltrain/tree/master/9_sycl_of_hell <https://github.com/kevin-harms/sycltrain/tree/master/9_sycl_of_hell>, they build correctly with the dpcpp/2019.6.30.011 module, but with dpcpp/2019.9.30.013 I get: clang++ -o 5_buffer_slm 5_buffer_slm.cpp -std=c++17 -fsycl -lOpenCL 5_buffer_slm.cpp:34:7: error: SYCL kernel cannot call a variadic function printf( "slm rank: %d \n", slm[world_rank % INT_MAX ]); ^ 1 error generated. Are there changes to the codes and/or to the build process needed for these to work with the new SDK? Thanks for your help, Nicholas Chaimov HPC Computer Scientist ParaTools, Inc. 1900 Millrace Drive, Box 1, Suite 104 Eugene, OR 97403 (503) 869-8513

1 0

Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK
by Rosales-fernandez, Carlos 24 Oct '19

24 Oct '19

Looks like the login nodes do not have a /etc/OpenCL/vendors entry, so the runtime can’t find the appropriate libraries and fails. I imagine this is done on purpose to avoid people running on the login node but, in any case, I tested the CPU driver provided in a Ubuntu and a RHEL system today and it looks like the CPU driver install is working as expected. Regards, Carlos From: "Hammond, Jeff R" <jeff.r.hammond(a)intel.com> Date: Thursday, October 24, 2019 at 10:47 AM To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov>, "Rosales-fernandez, Carlos" <carlos.rosales-fernandez(a)intel.com>, "Harms, Kevin" <harms(a)alcf.anl.gov> Cc: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK What OpenCL is installed on the login node? Brodman says Intel SYCL from GitHub plusoclcpuexp-2019.8.8.0.0822 works on his Xeon. Jeff From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov> Date: Thursday, October 24, 2019 at 7:47 AM To: "Rosales-fernandez, Carlos" <carlos.rosales-fernandez(a)intel.com>, "Kevin Harms (Argonne)" <harms(a)alcf.anl.gov> Cc: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Carlos, You’re right. I was running on a login node because I thought small tests were ok there, the software stack is the same, and I would try to get code running on the CPU first. I can confirm that the vector allocation and resize does indeed work as intended on an iris compute node. I’ll run on the compute nodes from now on. To answer Kevin’s question: using sycl::usm_allocator<int, sycl::usm::alloc::shared> alloc(ctxt, dev) causes the following error when running on the login node "terminate called after throwing an instance of 'cl::sycl::invalid_object_error’ what(): This instance of device is a host instance 0 (CL_SUCCESS)" But it also runs correctly on an iris compute node. Many thanks. Onward, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198 On Oct 24, 2019, at 7:54 AM, Rosales-fernandez, Carlos <carlos.rosales-fernandez(a)intel.com<mailto:[email protected]>> wrote: Thomas, When I tested the latest SDK the allocator_vector.cpp example worked correctly on the iris nodes, but it may segfault if you run on a login node (I only test building there, not execution) – can you confirm if you saw the segfault in a compute node? Carlos From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov<mailto:[email protected]>> Date: Wednesday, October 23, 2019 at 8:12 PM To: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Subject: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka<http://www.mcs.anl.gov/~tpeterka> phone: 630-252-7198

1 0

Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK
by Bertoni, Colleen 24 Oct '19

24 Oct '19

We do have opencl_expcpu/2019.8.8.0.0822 installed on JLSE (credit to Brian Homerding) in /soft/modulefiles. When I tried running allocator_vector.cpp with the public LLVM Sycl module, which loads opencl_expcpu, it ran without a segfault on a login node. (See below.) I am unsure what's going on exactly, but maybe the SDK does not have this yet? Thanks, Colleen [bertoni@jlselogin1 sycl]$ export MODULEPATH=/soft/restricted/CNDA/modulefiles:/soft/modulefiles [bertoni@jlselogin1 sycl]$ module load public_llvm_intel_sycl [bertoni@jlselogin1 sycl]$ clang++ -std=c++14 -fsycl alloc.cpp -lOpenCL [bertoni@jlselogin1 sycl]$ ./a.out ________________________________ From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov> on behalf of Hammond, Jeff R via Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Sent: Thursday, October 24, 2019 10:47 AM To: Peterka, Thomas <tpeterka(a)mcs.anl.gov>; Rosales-fernandez, Carlos <carlos.rosales-fernandez(a)intel.com>; Harms, Kevin <harms(a)alcf.anl.gov> Cc: Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK What OpenCL is installed on the login node? Brodman says Intel SYCL from GitHub plusoclcpuexp-2019.8.8.0.0822 works on his Xeon. Jeff From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov> Date: Thursday, October 24, 2019 at 7:47 AM To: "Rosales-fernandez, Carlos" <carlos.rosales-fernandez(a)intel.com>, "Kevin Harms (Argonne)" <harms(a)alcf.anl.gov> Cc: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Carlos, You’re right. I was running on a login node because I thought small tests were ok there, the software stack is the same, and I would try to get code running on the CPU first. I can confirm that the vector allocation and resize does indeed work as intended on an iris compute node. I’ll run on the compute nodes from now on. To answer Kevin’s question: using sycl::usm_allocator<int, sycl::usm::alloc::shared> alloc(ctxt, dev) causes the following error when running on the login node "terminate called after throwing an instance of 'cl::sycl::invalid_object_error’ what(): This instance of device is a host instance 0 (CL_SUCCESS)" But it also runs correctly on an iris compute node. Many thanks. Onward, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198 On Oct 24, 2019, at 7:54 AM, Rosales-fernandez, Carlos <carlos.rosales-fernandez(a)intel.com<mailto:[email protected]>> wrote: Thomas, When I tested the latest SDK the allocator_vector.cpp example worked correctly on the iris nodes, but it may segfault if you run on a login node (I only test building there, not execution) – can you confirm if you saw the segfault in a compute node? Carlos From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov<mailto:[email protected]>> Date: Wednesday, October 23, 2019 at 8:12 PM To: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Subject: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka<http://www.mcs.anl.gov/~tpeterka> phone: 630-252-7198

1 0

Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK
by Hammond, Jeff R 24 Oct '19

24 Oct '19

What OpenCL is installed on the login node? Brodman says Intel SYCL from GitHub plusoclcpuexp-2019.8.8.0.0822 works on his Xeon. Jeff From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov> Date: Thursday, October 24, 2019 at 7:47 AM To: "Rosales-fernandez, Carlos" <carlos.rosales-fernandez(a)intel.com>, "Kevin Harms (Argonne)" <harms(a)alcf.anl.gov> Cc: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Carlos, You’re right. I was running on a login node because I thought small tests were ok there, the software stack is the same, and I would try to get code running on the CPU first. I can confirm that the vector allocation and resize does indeed work as intended on an iris compute node. I’ll run on the compute nodes from now on. To answer Kevin’s question: using sycl::usm_allocator<int, sycl::usm::alloc::shared> alloc(ctxt, dev) causes the following error when running on the login node "terminate called after throwing an instance of 'cl::sycl::invalid_object_error’ what(): This instance of device is a host instance 0 (CL_SUCCESS)" But it also runs correctly on an iris compute node. Many thanks. Onward, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198 On Oct 24, 2019, at 7:54 AM, Rosales-fernandez, Carlos <carlos.rosales-fernandez(a)intel.com<mailto:[email protected]>> wrote: Thomas, When I tested the latest SDK the allocator_vector.cpp example worked correctly on the iris nodes, but it may segfault if you run on a login node (I only test building there, not execution) – can you confirm if you saw the segfault in a compute node? Carlos From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov<mailto:[email protected]>> Date: Wednesday, October 23, 2019 at 8:12 PM To: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Subject: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka<http://www.mcs.anl.gov/~tpeterka> phone: 630-252-7198

1 0

Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK
by Peterka, Thomas 24 Oct '19

24 Oct '19

Carlos, You’re right. I was running on a login node because I thought small tests were ok there, the software stack is the same, and I would try to get code running on the CPU first. I can confirm that the vector allocation and resize does indeed work as intended on an iris compute node. I’ll run on the compute nodes from now on. To answer Kevin’s question: using sycl::usm_allocator<int, sycl::usm::alloc::shared> alloc(ctxt, dev) causes the following error when running on the login node "terminate called after throwing an instance of 'cl::sycl::invalid_object_error’ what(): This instance of device is a host instance 0 (CL_SUCCESS)" But it also runs correctly on an iris compute node. Many thanks. Onward, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198 On Oct 24, 2019, at 7:54 AM, Rosales-fernandez, Carlos <carlos.rosales-fernandez(a)intel.com<mailto:[email protected]>> wrote: Thomas, When I tested the latest SDK the allocator_vector.cpp example worked correctly on the iris nodes, but it may segfault if you run on a login node (I only test building there, not execution) – can you confirm if you saw the segfault in a compute node? Carlos From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov<mailto:[email protected]>> Date: Wednesday, October 23, 2019 at 8:12 PM To: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Subject: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka<http://www.mcs.anl.gov/~tpeterka> phone: 630-252-7198

1 0

Re: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK
by Rosales-fernandez, Carlos 24 Oct '19

24 Oct '19

Thomas, When I tested the latest SDK the allocator_vector.cpp example worked correctly on the iris nodes, but it may segfault if you run on a login node (I only test building there, not execution) – can you confirm if you saw the segfault in a compute node? Carlos From: Ecp-aurora-sdk-discuss <ecp-aurora-sdk-discuss-bounces(a)lists.jlse.anl.gov> on behalf of "Peterka, Thomas via Ecp-aurora-sdk-discuss" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Reply-To: "Peterka, Thomas" <tpeterka(a)mcs.anl.gov> Date: Wednesday, October 23, 2019 at 8:12 PM To: "Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <Ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: [Ecp-aurora-sdk-discuss] allocating an STL vector in USM using SYCL w/ latest version of SDK Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198

1 0

allocating an STL vector in USM using SYCL w/ latest version of SDK
by Peterka, Thomas 23 Oct '19

23 Oct '19

Hi, I tried to compile and run a test of allocating a C++ std::vector using USM in the latest version of the SYCL SDK. I basically copied the code in this example: https://github.com/intel/llvm/blob/sycl/sycl/test/usm/allocator_vector.cp Here is a snippet of my code: #include <CL/sycl/usm/usm_allocator.hpp> // needed for usm_allocator using namespace cl; sycl::default_selector selector; sycl::queue q(selector); auto dev = q.get_device(); auto ctxt = q.get_context(); sycl::usm_allocator<int, sycl::usm::alloc::host> alloc(ctxt, dev); std::vector<int, decltype(alloc)> n(alloc); n.resize(2); // seg faults The last line, n.resize(2), seg faults. Trying to avoid the resizing by allocating a given size also seg faults: std::vector<int, decltype(alloc)> n(2, alloc); Can anyone confirm that allocating/resizing a nonzero-size vector works with the latest USM, or is this a bug? Thanks, Tom ----------------- Tom Peterka Mathematics and Computer Science Division Argonne National Laboratory 9700 S. Cass Ave. Lemont, IL 60439 Bldg 240, Rm 2148 e-mail: tpeterka(a)mcs.anl.gov<mailto:[email protected]> web: www.mcs.anl.gov/~tpeterka phone: 630-252-7198

1 0

Re: [Ecp-aurora-sdk-discuss] Intel LLVM SYCL on JLSE
by Homerding, Brian Daniel 16 Oct '19

16 Oct '19

Hi Paulius, You should now see both devices on the Iris nodes. Take Care, Brian From: "Velesko, Paulius" <pvelesko(a)anl.gov> Date: Saturday, October 12, 2019 at 4:24 PM To: "Homerding, Brian Daniel" <bhomerding(a)anl.gov>, "ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov> Subject: RE: Intel LLVM SYCL on JLSE Brian, I tested out USM from the main SDK drop. Both devices show up, and you can compile and run a USM code on the CPU device and get a result which is incorrect only a little (also tiny variances from run to run) No surprise there, I suppose, since CPU OpenCL device does not have usm preview extension. Slightly surprised that it runs at all and the result is pretty close. Best, Paulius From: Homerding, Brian Daniel Sent: Friday, October 11, 2019 4:07 PM To: Velesko, Paulius <pvelesko(a)anl.gov>; ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov Subject: Re: Intel LLVM SYCL on JLSE Hi Paulius, It is sitting on top of the public_opencl module which doesn’t currently have support for the OCL CPU device. We are looking into it and will get back to you. - Brian From: "Velesko, Paulius" <pvelesko(a)anl.gov<mailto:[email protected]>> Date: Friday, October 11, 2019 at 2:55 PM To: "Homerding, Brian Daniel" <bhomerding(a)anl.gov<mailto:[email protected]>>, "ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>" <ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>> Subject: RE: Intel LLVM SYCL on JLSE Brian, When I load this, I only see a GPU device. Is there a reason why CPU OCL is not getting loaded as well? -Paulius From: Intel-dga-discuss [mailto:[email protected]] On Behalf Of Homerding, Brian Daniel via Intel-dga-discuss Sent: Tuesday, October 8, 2019 11:02 AM To: ecp-aurora-sdk-discuss(a)lists.jlse.anl.gov<mailto:[email protected]>; intel-dga-discuss(a)lists.jlse.anl.gov<mailto:[email protected]> Subject: [Intel-dga-discuss] Intel LLVM SYCL on JLSE Hello all, Intel’s open source SYCL compiler has been installed on JLSE. This is from their staging area for contributing SYCL to LLVM. https://github.com/intel/llvm Quickstart: export MODULEPATH=/soft/modulefiles:${MODULEPATH} module load public_llvm_intel_sycl/20191004 clang++ -std=c++14 -fsycl mySyclFile.cpp -lOpenCL -lsycl Please let us know if you have any issues. Take care, Brian

1 0