-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add IntelLLVM support & Spack-based CI #36
Add IntelLLVM support & Spack-based CI #36
Conversation
a558dad
to
de5236d
Compare
Is LLVM object compatible. To test this properly I need to check it out,
and build codes with it. Successful build is sufficient for
gfsio because it is NEVER used in execution but for other libraries an
independent evaluator will need to build and run. Alternatively I can
just look at your test logs and approve them and the PR.
…On Thu, Nov 9, 2023 at 6:24 PM Alex Richert ***@***.***> wrote:
@AlexanderRichert-NOAA <https://github.com/AlexanderRichert-NOAA>
requested your review on: #36
<#36> Add IntelLLVM
support & Spack-based CI.
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANDS4FQ4HBZ5HQNJ4HYPKBTYDVQZJAVCNFSM6AAAAAA7FKD3EKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHEYTSMBQHEZTAMY>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
--
George W Vandenberghe
*Lynker Technologies at * NOAA/NWS/NCEP/EMC
5830 University Research Ct., Rm. 2141
College Park, MD 20740
***@***.***
301-683-3769(work) 3017751547(cell)
|
Object compatible with regular Intel ("classic")? I believe it's supposed to be, but in practice I don't think we'll ever mix them. In some sense this is preparing us for when whole stacks+models are built with the new compilers. We won't switch spack-stack over to LLVM/OneAPI on any given system until the applications that use them are ready. |
The applications that use them won't be ready even to compile until we have
the stacks built with the new compiler. Which brings up the question, are
modules (fortran .mod files) compatible. If not, we will have to build an
entire stack with the new compiler and then port the application builds.
A straightforward application that uses a lot of this stuff is UPP.
I am probably a good person to do that and yeah I know I am going to regret
saying that,
…On Thu, Nov 9, 2023 at 7:52 PM Alex Richert ***@***.***> wrote:
Object compatible with regular Intel ("classic")? I believe it's supposed
to be, but in practice I don't think we'll ever mix them. In some sense
this is preparing us for when whole stacks+models are built with the new
compilers. We won't switch spack-stack over to LLVM/OneAPI on any given
system until the applications that use them are ready.
—
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANDS4FURD627DVIBTSQOQNDYDV3DPAVCNFSM6AAAAAA7FKD3EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUHEYDIOJTGQ>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
--
George W Vandenberghe
*Lynker Technologies at * NOAA/NWS/NCEP/EMC
5830 University Research Ct., Rm. 2141
College Park, MD 20740
***@***.***
301-683-3769(work) 3017751547(cell)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice.
This PR adds IntelLLVM (OneAPI) support and adds a Spack-based CI workflow.
Fixes #32
Fixes #37
Supersedes #33