Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

To update defaults on various systems #118

Open
dipietrantonio opened this issue Sep 1, 2020 · 6 comments
Open

To update defaults on various systems #118

dipietrantonio opened this issue Sep 1, 2020 · 6 comments

Comments

@dipietrantonio
Copy link
Contributor

I suggest to drop gcc < 7 as default compilers on all systems if possible (not sure about crays). Also, we may want to update the default cuda etc.

@ddeeptimahanti
Copy link
Contributor

Agree- but gcc/4.8.5 is still the default on Zeus. MWA has special interest in using gcc/5.5.0 on Galaxy/other systems- some codes are to be ported

@marcodelapierre
Copy link
Contributor

Thanks for bringing this to the table @Halolegend94 .

In general I would agree for Zeus. For Magnus, I'd double check with Mark O, not sure about any Cray constraint.
One question though: do we have a strong reason to go ahead with this in the current systems, rather than postponing to the next one? Surely some maali builds take for ever because of the multiple compilers, but ... does it happen often these days? Just asking in the interest of best usage of staff time.

@ddeeptimahanti , if gcc/5.5.0 is of systematic use in any system then we should keep it in the defaults. Otherwise if it sporadic we can take it off; it doesn't mean it is banned from maali; it just means that it needs to be explicitly requested in the cygnet.

Two more notes:

  1. I would still build general purpose libraries (e.g. MPI, LAPACK, FFT, HDF5, ...) with all compilers, so they're ready for use for the "special" cases.
  2. If we go ahead with this, we will need to check the cygnet files for applications that NEED to use an older compiler.

@dipietrantonio
Copy link
Contributor Author

dipietrantonio commented Sep 2, 2020

It happened to me while building cmake on zeus. By the way, we should remove old cpu architectures right?

@marcodelapierre
Copy link
Contributor

marcodelapierre commented Sep 2, 2020

I have just removed KNL from Zeus!
For Sandybridge and the GCC versions I'd recommend a team discussion to evaluate, see email.

@dipietrantonio
Copy link
Contributor Author

dipietrantonio commented Sep 9, 2020

On magnus,

cdipietrantonio@nid00010:/scratch/pawsey0001/cdipietrantonio> echo $MAALI_DEFAULT_CPU_TARGET 
sandybridge ivybridge haswell

Software does not get compiled for broadwell which is the target architecture of the compute nodes if I am not mistaken. In fact I have compiled boost/.72.0 with this default and now I am having issues loading modules. Am I missing something here?

@marcodelapierre
Copy link
Contributor

mmh this needs to be double-checked with staff with more service than me, but I am pretty sure there's no broadwell on Magnus/Galaxy:
Magnus: haswell on both login and compute
Galaxy: ivybridge / sandybridge depending on workq or gpuq (can't recall which is which)

So I reckon the issue possibly comes from a different source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants