Support -arch=nec-sx-aurora and NEC compilers

[nchaimov]

TAU now supports the NEC SX Aurora architecture (-arch=nec-sx-aurora) and NEC compilers (ncc, nc++, mpinfort). These should be added to TAU Commander.

Differences when using TAU with NEC SX Aurora:

• when compiling with MPI, need -shared-mpi as argument

• when running tau_exec, must pass full path to tau_exec to mpiexec

A system is available at PRL with this accelerator at sx-aurora.nic.uoregon.edu from within the UO network.

[nchaimov]

NEC documentation at https://www.nec.com/en/global/prod/hpc/aurora/document/index.html

In particular, documentation on running programs on the accelerator is at https://www.hpc.nec/documents/guide/pdfs/ProgramExecutionQuickGuide_E.pdf

[khsa1]

@nchaimov The tau configure script downloads and builds zlib from source for BFD on NEC. I think we should continue to build handle dependencies through taucmdr rather than passing -bfd=download to the configure script, so what do you think would be the best way to handle this? Should zlib be added as another dependency to tau or since this only seems to have come up so far on NEC should it just be part of the build procedure for bfd?

[nchaimov]

I think that TAU Commander should probably handle zlib itself. It can cause problems on other platforms too. I’ve run into a problem before where the zlib headers aren’t installed by default on some Linux distros and so TAU Commander can’t build TAU correctly.

On Aug 9, 2020, at 12:32 PM, Samuel Khuvis [email protected] wrote:

 @nchaimov The tau configure script downloads and builds zlib from source for BFD on NEC. I think we should continue to build handle dependencies through taucmdr rather than passing -bfd=download to the configure script, so what do you think would be the best way to handle this? Should zlib be added as another dependency to tau or since this only seems to have come up so far on NEC should it just be part of the build procedure for bfd?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[khsa1]

Should we add a new option to the TAU configure script for the install path for zlib? There isn't really a good way to install zlib into BFD with tau commander and I don't think that's the best way to do it anyway.

[nchaimov]

That sounds reasonable. If the path isn't specified the configure script should behave the way it currently does.

[nchaimov]

Also, if you want to test libz downloading on a non-NEC architecture, recent Ubuntu releases don't include libz in build-essential so if you install Ubuntu 20.04 LTS in a VM, do apt-get install build-essential, and try to install TAU with BFD, linking will fail with /usr/bin/ld: cannot find -lz