- Intel-nda - mailman3.cels.anl.gov

Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs
by Kumaran, Kalyan 23 Sep '16

23 Sep '16

Do not forget to subscribe to the mailing list to track your bugs. On Sep 23, 2016, at 12:40 PM, Luo, Ye <yeluo(a)anl.gov<mailto:[email protected]>> wrote: Magically got it through at the 4th attempt. Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: Hammond, Jeff R [jeff.r.hammond(a)intel.com<mailto:[email protected]>] Sent: Friday, September 23, 2016 12:39 PM To: Kumaran, Kalyan; Luo, Ye Cc: intel-nda(a)jlse.anl.gov<mailto:[email protected]> Subject: Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs Far too many Intel websites assume Internet Explorer. Obviously, this a huge problem for those of us bipedal mammals who use Mac. I use Safari for IPS because of similar issues with other browsers. Chrome works but it may be fickle. I use Firefox with Intel websites only a means of last resort. Jeff From: <intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Kumaran, Kalyan" <kumaran(a)alcf.anl.gov<mailto:[email protected]>> Date: Friday, September 23, 2016 at 10:35 AM To: "Luo, Ye" <yeluo(a)anl.gov<mailto:[email protected]>> Cc: "intel-nda(a)jlse.anl.gov<mailto:[email protected]>" <intel-nda(a)jlse.anl.gov<mailto:[email protected]>> Subject: Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs Nope. That is the only way. -Kumar On Sep 23, 2016, at 12:34 PM, Luo, Ye <yeluo(a)anl.gov<mailto:[email protected]>> wrote: Hi Kumaran, I got compiler internal error with the released 17 compiler while the 17 beta worked well. I tried to report a compiler bug using your generic account. However, the premier website gives me an error when I clicked the submission after filling all the information and ask me to contact Intel support contact instead. I was trying to attach a tar of the source code (7KB) allowing Intel to reproduce my problem. It seems trigger some bugs in the website. Do you have other ways to get the report through? Thanks! Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]> [intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>] on behalf of Kumaran, Kalyan [kumaran(a)alcf.anl.gov<mailto:[email protected]>] Sent: Tuesday, September 13, 2016 6:54 PM To: intel-nda(a)jlse.anl.gov<mailto:[email protected]> Subject: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs I have set up a generic account to report software bugs back to Intel. Login at premier.intel.com<http://premier.intel.com/> Username: argonne-intel Password: ArgonneIntel16! Click on Intel Premier Support on the LHS panel. You should see the open Quad issues (basically a bug reported by Steve Pieper). Updates to the Quad issues are emailed to the mailing list argonne-intel(a)alcf.anl.gov<mailto:[email protected]> (yes, alcf domain). So you need to subscribe the list at: https://lists.alcf.anl.gov/mailman/listinfo/argonne-intel Be good about tracking your issue and providing feedback whenever Intel updates the quad. I will add this to our confluence site tomorrow. Thanks, Kumar P.S.: There might be an update to your Quad issue from Martyn.

1 0

Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs
by Luo, Ye 23 Sep '16

23 Sep '16

Magically got it through at the 4th attempt. Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: Hammond, Jeff R [jeff.r.hammond(a)intel.com] Sent: Friday, September 23, 2016 12:39 PM To: Kumaran, Kalyan; Luo, Ye Cc: intel-nda(a)jlse.anl.gov Subject: Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs Far too many Intel websites assume Internet Explorer. Obviously, this a huge problem for those of us bipedal mammals who use Mac. I use Safari for IPS because of similar issues with other browsers. Chrome works but it may be fickle. I use Firefox with Intel websites only a means of last resort. Jeff From: <intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Kumaran, Kalyan" <kumaran(a)alcf.anl.gov<mailto:[email protected]>> Date: Friday, September 23, 2016 at 10:35 AM To: "Luo, Ye" <yeluo(a)anl.gov<mailto:[email protected]>> Cc: "intel-nda(a)jlse.anl.gov<mailto:[email protected]>" <intel-nda(a)jlse.anl.gov<mailto:[email protected]>> Subject: Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs Nope. That is the only way. -Kumar On Sep 23, 2016, at 12:34 PM, Luo, Ye <yeluo(a)anl.gov<mailto:[email protected]>> wrote: Hi Kumaran, I got compiler internal error with the released 17 compiler while the 17 beta worked well. I tried to report a compiler bug using your generic account. However, the premier website gives me an error when I clicked the submission after filling all the information and ask me to contact Intel support contact instead. I was trying to attach a tar of the source code (7KB) allowing Intel to reproduce my problem. It seems trigger some bugs in the website. Do you have other ways to get the report through? Thanks! Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]> [intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>] on behalf of Kumaran, Kalyan [kumaran(a)alcf.anl.gov<mailto:[email protected]>] Sent: Tuesday, September 13, 2016 6:54 PM To: intel-nda(a)jlse.anl.gov<mailto:[email protected]> Subject: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs I have set up a generic account to report software bugs back to Intel. Login at premier.intel.com<http://premier.intel.com/> Username: argonne-intel Password: ArgonneIntel16! Click on Intel Premier Support on the LHS panel. You should see the open Quad issues (basically a bug reported by Steve Pieper). Updates to the Quad issues are emailed to the mailing list argonne-intel(a)alcf.anl.gov<mailto:[email protected]> (yes, alcf domain). So you need to subscribe the list at: https://lists.alcf.anl.gov/mailman/listinfo/argonne-intel Be good about tracking your issue and providing feedback whenever Intel updates the quad. I will add this to our confluence site tomorrow. Thanks, Kumar P.S.: There might be an update to your Quad issue from Martyn.

1 0

Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs
by Hammond, Jeff R 23 Sep '16

23 Sep '16

Far too many Intel websites assume Internet Explorer. Obviously, this a huge problem for those of us bipedal mammals who use Mac. I use Safari for IPS because of similar issues with other browsers. Chrome works but it may be fickle. I use Firefox with Intel websites only a means of last resort. Jeff From: <intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>> on behalf of "Kumaran, Kalyan" <kumaran(a)alcf.anl.gov<mailto:[email protected]>> Date: Friday, September 23, 2016 at 10:35 AM To: "Luo, Ye" <yeluo(a)anl.gov<mailto:[email protected]>> Cc: "intel-nda(a)jlse.anl.gov<mailto:[email protected]>" <intel-nda(a)jlse.anl.gov<mailto:[email protected]>> Subject: Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs Nope. That is the only way. -Kumar On Sep 23, 2016, at 12:34 PM, Luo, Ye <yeluo(a)anl.gov<mailto:[email protected]>> wrote: Hi Kumaran, I got compiler internal error with the released 17 compiler while the 17 beta worked well. I tried to report a compiler bug using your generic account. However, the premier website gives me an error when I clicked the submission after filling all the information and ask me to contact Intel support contact instead. I was trying to attach a tar of the source code (7KB) allowing Intel to reproduce my problem. It seems trigger some bugs in the website. Do you have other ways to get the report through? Thanks! Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]> [intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>] on behalf of Kumaran, Kalyan [kumaran(a)alcf.anl.gov<mailto:[email protected]>] Sent: Tuesday, September 13, 2016 6:54 PM To: intel-nda(a)jlse.anl.gov<mailto:[email protected]> Subject: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs I have set up a generic account to report software bugs back to Intel. Login at premier.intel.com<http://premier.intel.com/> Username: argonne-intel Password: ArgonneIntel16! Click on Intel Premier Support on the LHS panel. You should see the open Quad issues (basically a bug reported by Steve Pieper). Updates to the Quad issues are emailed to the mailing list argonne-intel(a)alcf.anl.gov<mailto:[email protected]> (yes, alcf domain). So you need to subscribe the list at: https://lists.alcf.anl.gov/mailman/listinfo/argonne-intel Be good about tracking your issue and providing feedback whenever Intel updates the quad. I will add this to our confluence site tomorrow. Thanks, Kumar P.S.: There might be an update to your Quad issue from Martyn.

1 0

Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs
by Kumaran, Kalyan 23 Sep '16

23 Sep '16

Nope. That is the only way. -Kumar On Sep 23, 2016, at 12:34 PM, Luo, Ye <yeluo(a)anl.gov<mailto:[email protected]>> wrote: Hi Kumaran, I got compiler internal error with the released 17 compiler while the 17 beta worked well. I tried to report a compiler bug using your generic account. However, the premier website gives me an error when I clicked the submission after filling all the information and ask me to contact Intel support contact instead. I was trying to attach a tar of the source code (7KB) allowing Intel to reproduce my problem. It seems trigger some bugs in the website. Do you have other ways to get the report through? Thanks! Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]> [intel-nda-bounces(a)lists.jlse.anl.gov<mailto:[email protected]>] on behalf of Kumaran, Kalyan [kumaran(a)alcf.anl.gov<mailto:[email protected]>] Sent: Tuesday, September 13, 2016 6:54 PM To: intel-nda(a)jlse.anl.gov<mailto:[email protected]> Subject: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs I have set up a generic account to report software bugs back to Intel. Login at premier.intel.com<http://premier.intel.com/> Username: argonne-intel Password: ArgonneIntel16! Click on Intel Premier Support on the LHS panel. You should see the open Quad issues (basically a bug reported by Steve Pieper). Updates to the Quad issues are emailed to the mailing list argonne-intel(a)alcf.anl.gov<mailto:[email protected]> (yes, alcf domain). So you need to subscribe the list at: https://lists.alcf.anl.gov/mailman/listinfo/argonne-intel Be good about tracking your issue and providing feedback whenever Intel updates the quad. I will add this to our confluence site tomorrow. Thanks, Kumar P.S.: There might be an update to your Quad issue from Martyn.

1 0

Re: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs
by Luo, Ye 23 Sep '16

23 Sep '16

Hi Kumaran, I got compiler internal error with the released 17 compiler while the 17 beta worked well. I tried to report a compiler bug using your generic account. However, the premier website gives me an error when I clicked the submission after filling all the information and ask me to contact Intel support contact instead. I was trying to attach a tar of the source code (7KB) allowing Intel to reproduce my problem. It seems trigger some bugs in the website. Do you have other ways to get the report through? Thanks! Ye =================== Ye Luo, Ph.D. Leadership Computing Facility Argonne National Laboratory ________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov [intel-nda-bounces(a)lists.jlse.anl.gov] on behalf of Kumaran, Kalyan [kumaran(a)alcf.anl.gov] Sent: Tuesday, September 13, 2016 6:54 PM To: intel-nda(a)jlse.anl.gov Subject: [JLSE-Intel-NDA] Reporting Intel compiler, tools bugs I have set up a generic account to report software bugs back to Intel. Login at premier.intel.com<http://premier.intel.com> Username: argonne-intel Password: ArgonneIntel16! Click on Intel Premier Support on the LHS panel. You should see the open Quad issues (basically a bug reported by Steve Pieper). Updates to the Quad issues are emailed to the mailing list argonne-intel(a)alcf.anl.gov<mailto:[email protected]> (yes, alcf domain). So you need to subscribe the list at: https://lists.alcf.anl.gov/mailman/listinfo/argonne-intel Be good about tracking your issue and providing feedback whenever Intel updates the quad. I will add this to our confluence site tomorrow. Thanks, Kumar P.S.: There might be an update to your Quad issue from Martyn.

1 0

[JLSE-Intel-NDA] XPPSL Zonesort Module
by Allen, Benjamin S. 23 Sep '16

23 Sep '16

The KNL systems now have the zonesort_module kernel module from XPPSL 1.4.1 loaded on boot, and permissions set on /sys/kernel/zone_sort_free_pages/nodeid to allow users to echo the memory numa node into it to trigger a sort. More details in the attached user guide in section 8. Note, I didn't apply this change to running systems, so you won't see the module loaded until the machine is rebooted. Ben

1 0

Re: [JLSE-Intel-NDA] OpenMP bug in Intel Fortran compiler
by Allen, Benjamin S. 23 Sep '16

23 Sep '16

Disregard. Cleaning out old moderated messages. Ben > On Jul 28, 2016, at 6:52 PM, Kumaran, Kalyan <kumaran(a)alcf.anl.gov> wrote: > > Thanks, Martyn! I will open a Quad once I create a generic account. I have copied Steve Pieper to this thread. He reported the issue. > > -Kumar > > >> On Jul 28, 2016, at 6:42 PM, Corden, Martyn J <martyn.j.corden(a)intel.com> wrote: >> >> Hello Kumar! >> Nice to hear from you. I shall be looking into your WORKSHARE issue, but haven’t yet had chance to do more than just reproduce.. We’ll want to create a support issue out of it eventually, so that it can be tracked. Thanks for the small test case. >> It’s only recently that the Intel Fortran compiler has made a parallel implementation of WORKSHARE, so it still has some restrictions. It looks like the loop over the index variable is challenging. >> >> Regards, >> Martyn >> >> From: Kirkendall, Keith G >> Sent: Thursday, July 28, 2016 7:05 AM >> To: Kumaran, Kalyan >> Cc: Corden, Martyn J; Borges, Leonardo; Allison, CM; Fromkin, Russ >> Subject: RE: [JLSE-Intel-NDA] OpenMP bug in Intel Fortran compiler >> >> I don’t think we mind if ANL wants to use a combined, single account. >> >> From: Kumaran, Kalyan [mailto:[email protected]] >> Sent: Wednesday, July 27, 2016 8:49 PM >> To: Kirkendall, Keith G <keith.g.kirkendall(a)intel.com> >> Cc: Corden, Martyn J <martyn.j.corden(a)intel.com>; Borges, Leonardo <leonardo.borges(a)intel.com>; Allison, CM <cm.allison(a)intel.com>; Fromkin, Russ <russ.fromkin(a)intel.com> >> Subject: Re: [JLSE-Intel-NDA] OpenMP bug in Intel Fortran compiler >> >> I know Martyn from my SGI days as he was my main contact for the top 20 Itanium compiler bugs. Hello Martyn! >> >> Keith, regarding premier, do you want each user to open an account. I was hoping to set up a generic Argonne account that all users can use. Please advise. >> >> Thanks, >> Kumar >> >> >> On Jul 27, 2016, at 5:29 PM, Kirkendall, Keith G <keith.g.kirkendall(a)intel.com> wrote: >> >> Hi Kumar, >> Martyn Corden is the smart compiler guy that was recommended to me. As an aside, he’ll be supporting the Theta ESP workshop, so you’ll meet him FTF in August. >> The general process for compiler bugs is to file a ticket through premier.intel.com through your support account, but since we like you, you get Martyn directly this time. J >> >> Martyn, I copied the original email & files here. >> >> Thanks >> Keith >> >> From: Kumaran, Kalyan [mailto:[email protected]] >> Sent: Thursday, July 21, 2016 4:11 PM >> To: Allison, CM <cm.allison(a)intel.com>; Kirkendall, Keith G <keith.g.kirkendall(a)intel.com> >> Cc: Fromkin, Russ <russ.fromkin(a)intel.com> >> Subject: Fwd: [JLSE-Intel-NDA] OpenMP bug in Intel Fortran compiler >> >> How do we report compiler bugs? Happens in 2016 and 2017 versions. >> >> -Kumar >> >> >> >> Begin forwarded message: >> >> From: "Steven C. Pieper" <spieper(a)anl.gov> >> Subject: [JLSE-Intel-NDA] OpenMP bug in Intel Fortran compiler >> Date: July 12, 2016 at 1:55:50 PM CDT >> To: <intel-nda(a)lists.jlse.anl.gov> >> Reply-To: <spieper(a)anl.gov> >> >> I have attached a simplified source code and demonstration script >> to show an OpenMP bug in the Intel Fortran compiler. I am using >> >> /soft/compilers/intel_beta/compilers_and_libraries_2017.0.042/linux/bin/intel64/ifort >> >> The bug occurs on both the jlse login node and knl00. It >> occurs using two or more OpenMP threads, but not if only >> one thread is used. The demonstration uses no optimization >> (O0) but the bug also happens with optimization. >> It does not happen on the IBM BG/Q. >> >> The bug is a segfault at line 113 of the source file: >> >> !$OMP PARALLEL WORKSHARE >> cof(:,:,1:min(2,num_op_emew),:,:) = 0 >> cfcl(:,:,:,:) = 0.d0 >> !$OMP END PARALLEL WORKSHARE >> >> It is triggered by line 128 when that line is activated (in the >> source file it is commented): >> >> cof(:,:,2,iqcross(:),1) = cof(:,:,1,iqcross(:),1) + cof(:,:,2,iqcross(:),1) >> >> The problem is the index iqcross(:); iqcross is a 2-element array >> with valid values as are printed. If this line is replaced by >> the equivalent two lines that follow: >> >> cof(:,:,2,iqcross(1),1) = cof(:,:,1,iqcross(1),1) + cof(:,:,2,iqcross(1),1) >> cof(:,:,2,iqcross(2),1) = cof(:,:,1,iqcross(2),1) + cof(:,:,2,iqcross(2),1) >> >> no segfault occurs. Note also that in fact this section of the >> code will never be reached due to the stop at line 119 and the if at >> line 121 which is false. In the original large code, this >> second OMP section was more than 100 lines removed from the first >> with a large intermediate OMP section. >> >> The script first compiles and runs the source with the commented >> line (bug-ok.f). This shows that things work with the line removed. >> Then the script uses sed to uncomment the line into bug-bad.f and >> compiles and runs that. This causes the segfault. >> >> Steve >> >> >> >> -- >> Steven C. Pieper, Senior Physicist Emeritus: spieper(a)anl.gov >> Argonne National Laboratory, Physics Division, Bldg. 203, Argonne, IL 60439 >> Phone: 630-252-4232 Fax -6008 Secretary, Debra Beres, -4100 >> http://www.phy.anl.gov/theory/staff/scp.html >> _______________________________________________ >> Intel-nda mailing list >> Intel-nda(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >> >> <makebug.txt><bug-ok.f> > > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

Re: [JLSE-Intel-NDA] libifport error
by Allen, Benjamin S. 23 Sep '16

23 Sep '16

Another tip you shouldn't need to set INTEL_LICENSE_FILE anymore. The compilers (and other Intel tools) look for a license file in the install which redirects them to the server. Ben > On Sep 23, 2016, at 11:45 AM, François Tessier <ftessier(a)anl.gov> wrote: > > Ok, good to know. It seems to resolve the issue. With this > configuration, I'm able to compile and run a simple MPI "Hello world" > example on a KNL node using the Intel compiler. > > --------------------- > export INTEL_LICENSE_FILE=28518@ftsn2 > source > /soft/compilers/intel/compilers_and_libraries/linux/bin/compilervars.sh > intel64 > source /soft/compilers/intel/vtune_amplifier_xe/amplxe-vars.sh > source /soft/compilers/intel/advisor/advixe-vars.sh > source /soft/compilers/intel/inspector/inspxe-vars.sh > source > /soft/compilers/intel/compilers_and_libraries/linux/mpi/bin64/mpivars.sh > --------------------- > > Thanks, > > François > > On 09/23/2016 11:37 AM, Allen, Benjamin S. wrote: >> The compilers, etc in /soft/compilers/intel are the GA release of 2017 now. They're newer than 2017 beta which is installed in /soft/compilers/intel_beta. You should be using the newer version. If someone works with the beta version and not the GA that also should be filed as a bug. >> >> Ben >> >>> On Sep 23, 2016, at 10:55 AM, François Tessier <ftessier(a)anl.gov> wrote: >>> >>> Hi, >>> >>> It works with mpiicc instead of mpicc. I updated all the paths to use >>> intel_beta. However, even if the compilation succeeds, a call to mpirun >>> gives the same error related to "for_ifcore_version". Is there a >>> specific wrapper to use instead of mpirun to run the application on KNL? >>> >>> Maybe all of this should be added to http://jlse.anl.gov/installed-software/ >>> >>> Thanks, >>> >>> François >>> >>> On 09/22/2016 10:42 PM, Hammond, Jeff R wrote: >>>> Why do you mix >>>> /soft/compilers/intel_beta >>>> >>>> and >>>> /soft/compilers/intel >>>> >>>> ? >>>> >>>> Jeff >>>> >>>> On 9/22/16, 1:42 PM, "intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >>>> François Tessier" <intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >>>> ftessier(a)anl.gov> wrote: >>>> >>>>> Hi All, >>>>> >>>>> I'm trying to compile a MPI application with the Intel Compiler for KNL. >>>>> However, I have issues like that: >>>>> >>>>> ----------------------- >>>>> --> mpicc -g -O3 -xMIC-AVX512 hello.c -o hello >>>>> /soft/compilers/intel_beta/compilers_and_libraries_2017.0.042/linux/compil >>>>> er/lib/intel64/libifport.so.5: >>>>> undefined reference to `for_ifcore_version' >>>>> ----------------------- >>>>> >>>>> According to some posts on Intel forums, it seems to come from a >>>>> conflict between the mpivars.sh script and $PATH and $LD_LIBRARY_PATH >>>>> set for mpich-intel-3.1.4. I tried several combinations of these but >>>>> without any success. Here is the configuration I use: >>>>> >>>>> ----------------------- >>>>> export INTEL_LICENSE_FILE=28518@ftsn2 >>>>> source >>>>> /soft/compilers/intel_beta/compilers_and_libraries/linux/bin/compilervars. >>>>> sh >>>>> intel64 >>>>> source /soft/compilers/intel/vtune_amplifier_xe/amplxe-vars.sh >>>>> source /soft/compilers/intel/advisor_xe/advixe-vars.sh >>>>> source /soft/compilers/intel/inspector_xe/inspxe-vars.sh >>>>> #source >>>>> /soft/compilers/intel_beta/impi/2017.0.042/bin64/mpivars.sh >>>>> >>>>> >>>>> >>>>> export PATH=/soft/libraries/mpi/mpich-intel-3.1.4/bin:$PATH >>>>> export >>>>> LD_LIBRARY_PATH=/soft/libraries/mpi/mpich-intel-3.1.4/lib:$LD_LIBRARY_PATH >>>>> ----------------------- >>>>> >>>>> To confirm that MPI is set properly: >>>>> >>>>> ----------------------- >>>>> --> mpicc --version >>>>> icc (ICC) 17.0.0 20160315 >>>>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>>>> --> mpif90 --version >>>>> ifort (IFORT) 17.0.0 20160315 >>>>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>>>> ----------------------- >>>>> >>>>> Any idea? >>>>> >>>>> Thanks, >>>>> >>>>> François >>>>> >>>>> -- >>>>> -- >>>>> François TESSIER, Ph.D. >>>>> Postdoctoral Appointee >>>>> Argonne National Laboratory >>>>> LCF Division - Bldg 240, 4E 19 >>>>> Tel : +1 (630)-252-5068 >>>>> http://www.francoistessier.info >>>>> >>>>> _______________________________________________ >>>>> Intel-nda mailing list >>>>> Intel-nda(a)lists.jlse.anl.gov >>>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >>> -- >>> -- >>> François TESSIER, Ph.D. >>> Postdoctoral Appointee >>> Argonne National Laboratory >>> LCF Division - Bldg 240, 4E 19 >>> Tel : +1 (630)-252-5068 >>> http://www.francoistessier.info >>> >>> _______________________________________________ >>> Intel-nda mailing list >>> Intel-nda(a)lists.jlse.anl.gov >>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda > > -- > -- > François TESSIER, Ph.D. > Postdoctoral Appointee > Argonne National Laboratory > LCF Division - Bldg 240, 4E 19 > Tel : +1 (630)-252-5068 > http://www.francoistessier.info >

1 0

Re: [JLSE-Intel-NDA] libifport error
by François Tessier 23 Sep '16

23 Sep '16

Ok, good to know. It seems to resolve the issue. With this configuration, I'm able to compile and run a simple MPI "Hello world" example on a KNL node using the Intel compiler. --------------------- export INTEL_LICENSE_FILE=28518@ftsn2 source /soft/compilers/intel/compilers_and_libraries/linux/bin/compilervars.sh intel64 source /soft/compilers/intel/vtune_amplifier_xe/amplxe-vars.sh source /soft/compilers/intel/advisor/advixe-vars.sh source /soft/compilers/intel/inspector/inspxe-vars.sh source /soft/compilers/intel/compilers_and_libraries/linux/mpi/bin64/mpivars.sh --------------------- Thanks, Franï¿½ois On 09/23/2016 11:37 AM, Allen, Benjamin S. wrote: > The compilers, etc in /soft/compilers/intel are the GA release of 2017 now. They're newer than 2017 beta which is installed in /soft/compilers/intel_beta. You should be using the newer version. If someone works with the beta version and not the GA that also should be filed as a bug. > > Ben > >> On Sep 23, 2016, at 10:55 AM, Franï¿½ois Tessier <ftessier(a)anl.gov> wrote: >> >> Hi, >> >> It works with mpiicc instead of mpicc. I updated all the paths to use >> intel_beta. However, even if the compilation succeeds, a call to mpirun >> gives the same error related to "for_ifcore_version". Is there a >> specific wrapper to use instead of mpirun to run the application on KNL? >> >> Maybe all of this should be added to http://jlse.anl.gov/installed-software/ >> >> Thanks, >> >> Franï¿½ois >> >> On 09/22/2016 10:42 PM, Hammond, Jeff R wrote: >>> Why do you mix >>> /soft/compilers/intel_beta >>> >>> and >>> /soft/compilers/intel >>> >>> ? >>> >>> Jeff >>> >>> On 9/22/16, 1:42 PM, "intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >>> Franï¿½ois Tessier" <intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >>> ftessier(a)anl.gov> wrote: >>> >>>> Hi All, >>>> >>>> I'm trying to compile a MPI application with the Intel Compiler for KNL. >>>> However, I have issues like that: >>>> >>>> ----------------------- >>>> --> mpicc -g -O3 -xMIC-AVX512 hello.c -o hello >>>> /soft/compilers/intel_beta/compilers_and_libraries_2017.0.042/linux/compil >>>> er/lib/intel64/libifport.so.5: >>>> undefined reference to `for_ifcore_version' >>>> ----------------------- >>>> >>>> According to some posts on Intel forums, it seems to come from a >>>> conflict between the mpivars.sh script and $PATH and $LD_LIBRARY_PATH >>>> set for mpich-intel-3.1.4. I tried several combinations of these but >>>> without any success. Here is the configuration I use: >>>> >>>> ----------------------- >>>> export INTEL_LICENSE_FILE=28518@ftsn2 >>>> source >>>> /soft/compilers/intel_beta/compilers_and_libraries/linux/bin/compilervars. >>>> sh >>>> intel64 >>>> source /soft/compilers/intel/vtune_amplifier_xe/amplxe-vars.sh >>>> source /soft/compilers/intel/advisor_xe/advixe-vars.sh >>>> source /soft/compilers/intel/inspector_xe/inspxe-vars.sh >>>> #source >>>> /soft/compilers/intel_beta/impi/2017.0.042/bin64/mpivars.sh >>>> >>>> >>>> >>>> export PATH=/soft/libraries/mpi/mpich-intel-3.1.4/bin:$PATH >>>> export >>>> LD_LIBRARY_PATH=/soft/libraries/mpi/mpich-intel-3.1.4/lib:$LD_LIBRARY_PATH >>>> ----------------------- >>>> >>>> To confirm that MPI is set properly: >>>> >>>> ----------------------- >>>> --> mpicc --version >>>> icc (ICC) 17.0.0 20160315 >>>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>>> --> mpif90 --version >>>> ifort (IFORT) 17.0.0 20160315 >>>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>>> ----------------------- >>>> >>>> Any idea? >>>> >>>> Thanks, >>>> >>>> Franï¿½ois >>>> >>>> -- >>>> -- >>>> Franï¿½ois TESSIER, Ph.D. >>>> Postdoctoral Appointee >>>> Argonne National Laboratory >>>> LCF Division - Bldg 240, 4E 19 >>>> Tel : +1 (630)-252-5068 >>>> http://www.francoistessier.info >>>> >>>> _______________________________________________ >>>> Intel-nda mailing list >>>> Intel-nda(a)lists.jlse.anl.gov >>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >> -- >> -- >> Franï¿½ois TESSIER, Ph.D. >> Postdoctoral Appointee >> Argonne National Laboratory >> LCF Division - Bldg 240, 4E 19 >> Tel : +1 (630)-252-5068 >> http://www.francoistessier.info >> >> _______________________________________________ >> Intel-nda mailing list >> Intel-nda(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda -- -- Franï¿½ois TESSIER, Ph.D. Postdoctoral Appointee Argonne National Laboratory LCF Division - Bldg 240, 4E 19 Tel : +1 (630)-252-5068 http://www.francoistessier.info

1 0

Re: [JLSE-Intel-NDA] libifport error
by Allen, Benjamin S. 23 Sep '16

23 Sep '16

The compilers, etc in /soft/compilers/intel are the GA release of 2017 now. They're newer than 2017 beta which is installed in /soft/compilers/intel_beta. You should be using the newer version. If someone works with the beta version and not the GA that also should be filed as a bug. Ben > On Sep 23, 2016, at 10:55 AM, François Tessier <ftessier(a)anl.gov> wrote: > > Hi, > > It works with mpiicc instead of mpicc. I updated all the paths to use > intel_beta. However, even if the compilation succeeds, a call to mpirun > gives the same error related to "for_ifcore_version". Is there a > specific wrapper to use instead of mpirun to run the application on KNL? > > Maybe all of this should be added to http://jlse.anl.gov/installed-software/ > > Thanks, > > François > > On 09/22/2016 10:42 PM, Hammond, Jeff R wrote: >> Why do you mix >> /soft/compilers/intel_beta >> >> and >> /soft/compilers/intel >> >> ? >> >> Jeff >> >> On 9/22/16, 1:42 PM, "intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >> François Tessier" <intel-nda-bounces(a)lists.jlse.anl.gov on behalf of >> ftessier(a)anl.gov> wrote: >> >>> Hi All, >>> >>> I'm trying to compile a MPI application with the Intel Compiler for KNL. >>> However, I have issues like that: >>> >>> ----------------------- >>> --> mpicc -g -O3 -xMIC-AVX512 hello.c -o hello >>> /soft/compilers/intel_beta/compilers_and_libraries_2017.0.042/linux/compil >>> er/lib/intel64/libifport.so.5: >>> undefined reference to `for_ifcore_version' >>> ----------------------- >>> >>> According to some posts on Intel forums, it seems to come from a >>> conflict between the mpivars.sh script and $PATH and $LD_LIBRARY_PATH >>> set for mpich-intel-3.1.4. I tried several combinations of these but >>> without any success. Here is the configuration I use: >>> >>> ----------------------- >>> export INTEL_LICENSE_FILE=28518@ftsn2 >>> source >>> /soft/compilers/intel_beta/compilers_and_libraries/linux/bin/compilervars. >>> sh >>> intel64 >>> source /soft/compilers/intel/vtune_amplifier_xe/amplxe-vars.sh >>> source /soft/compilers/intel/advisor_xe/advixe-vars.sh >>> source /soft/compilers/intel/inspector_xe/inspxe-vars.sh >>> #source >>> /soft/compilers/intel_beta/impi/2017.0.042/bin64/mpivars.sh >>> >>> >>> >>> export PATH=/soft/libraries/mpi/mpich-intel-3.1.4/bin:$PATH >>> export >>> LD_LIBRARY_PATH=/soft/libraries/mpi/mpich-intel-3.1.4/lib:$LD_LIBRARY_PATH >>> ----------------------- >>> >>> To confirm that MPI is set properly: >>> >>> ----------------------- >>> --> mpicc --version >>> icc (ICC) 17.0.0 20160315 >>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>> --> mpif90 --version >>> ifort (IFORT) 17.0.0 20160315 >>> Copyright (C) 1985-2016 Intel Corporation. All rights reserved. >>> ----------------------- >>> >>> Any idea? >>> >>> Thanks, >>> >>> François >>> >>> -- >>> -- >>> François TESSIER, Ph.D. >>> Postdoctoral Appointee >>> Argonne National Laboratory >>> LCF Division - Bldg 240, 4E 19 >>> Tel : +1 (630)-252-5068 >>> http://www.francoistessier.info >>> >>> _______________________________________________ >>> Intel-nda mailing list >>> Intel-nda(a)lists.jlse.anl.gov >>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda > > -- > -- > François TESSIER, Ph.D. > Postdoctoral Appointee > Argonne National Laboratory > LCF Division - Bldg 240, 4E 19 > Tel : +1 (630)-252-5068 > http://www.francoistessier.info > > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0