Skip to content

add support for using oneAPI versions of 'intel' toolchain components #3665

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

Merged
merged 6 commits into from
May 17, 2021

Conversation

boegel
Copy link
Member

@boegel boegel commented Apr 28, 2021

The iimpi toolchain definition had to be enhanced to discriminate between the oneAPI generation (iimpi version 2020.12 and newer), and the "classic" generation. No changes are needed for the intel toolchain itself (since that just derives from iimpi and adds MKL).

The det_subtoolchain_version function was enhanced to accept alternative subtoolchain names, since we don't know whether intel-compilers (for the oneAPI generation) or iccifort is the actual subtoolchain for iimpi until we can check the version, which we can't until there's an actual instance of the Toochain class...

Other toolchains that use the Intel compilers will need to be tweaked in a similar way, but iimpi is the more important one in the short term (for intel/2021a).

…native subtoolchain names rather than just one
…s iimpi + make sure correct _set_compiler_vars and set_variables methods are called
@boegel boegel force-pushed the oneapi branch 2 times, most recently from cd04da1 to 0da2987 Compare May 16, 2021 20:11
Copy link
Member

@migueldiascosta migueldiascosta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@migueldiascosta
Copy link
Member

Going in, thanks @boegel!

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

Successfully merging this pull request may close these issues.

2 participants