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

Remove classic intel compiler in favour of oneapi@2024 #262

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

JamesEdgeley
Copy link
Contributor

Description

Recent developments to NESO and NESO-Particles require using a later oneapi compiler version e.g. 2024. This no longer has the classic compilers in. See issue #260.
Spack 0.19 does not have oneapi@2024 so README updated to suggest using later version. See issue #261

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change)
  • Requires documentation updates

Testing

Please describe the tests that you ran to verify your changes and provide instructions for reproducibility. Please also list any relevant details for your test configuration.

  • Test Foo in /test/path/to/file_for_test_Foo.cpp
  • Description of test Foo
  • Test Bar in /test/path/to/file_for_test_Bar.cpp
  • Description of test Bar

Test Configuration:

  • OS:
  • SYCL implementation:
  • MPI details:
  • Hardware:

Checklist:

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any new dependencies are automatically built for users via cmake
  • I have used understandable variable names
  • I have run clang-format against my *.hpp and *.cpp changes
  • I have run cmake-format against my changes to CMakeLists.txt
  • I have run black against changes to *.py
  • I have made corresponding changes to the documentation
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings

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