-
Notifications
You must be signed in to change notification settings - Fork 51
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
Spack section #635
Spack section #635
Conversation
spack info kokkos | ||
|
||
|
||
Note that CPU micro-architectures are automatically inherited from Spack's configuration. |
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.
I don't quite understand that sentence.
Does that mean Spack is auto-detecting your CPU arch and passing flags to Kokkos?
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.
Yes, Spack always sets CPU micro-architecture and we follow this setting. It is most likely autoselected, but it can be set by hand, too.
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.
Yes my understanding spack auto detects it to give a default value to arch
. Then the Kokkos recipe does the mapping to the corresponding Kokkos ARCH
option.
As @cedricchevalier19 said, if needed you can manually specify arch
.
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.
That looks already good to me. I have a question regarding how far should we go:
- do we explain other packages like Kokkos Kernels, Kokkos-fft, Kokkos Tools... ? Maybe only Kokkos Tools has some specificity ?
- I see you mention the develop branch. Maybe we should write the text having spack version 1 in mind ?
Co-authored-by: Thomas Padioleau <[email protected]>
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.
Looks almost good to me.
Co-authored-by: Thomas Padioleau <[email protected]>
Thank you! |
Try explain: