Skip to content

[AMD][rocm-openmp-extras] - Updates for 4.3.1 and 4.5.0.#27653

Merged
alalazo merged 3 commits intospack:developfrom
estewart08:rocm-openmp-extras-4-5
Feb 1, 2022
Merged

[AMD][rocm-openmp-extras] - Updates for 4.3.1 and 4.5.0.#27653
alalazo merged 3 commits intospack:developfrom
estewart08:rocm-openmp-extras-4-5

Conversation

@estewart08
Copy link
Copy Markdown
Contributor

@srekolam srekolam requested review from haampie and trws January 14, 2022 02:40
@srekolam
Copy link
Copy Markdown
Contributor

@haampie @trws can we get the review for this ?

Comment on lines 197 to +198
# argument. This is fixed in later versions.
if self.spec.version == Version('4.3.0'):
if self.spec.version >= Version('4.3.0'):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

If the strip is fixed in later versions, why is the check a greater than?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Unfortunately, the small patch was not promoted to the release I originally thought. I expect this change to be in 5.0 and this condition will be updated once released.

@trws
Copy link
Copy Markdown
Contributor

trws commented Jan 14, 2022 via email

@estewart08
Copy link
Copy Markdown
Contributor Author

Makes sense, but in that case should we keep the comment or maybe make it a TODO so it doesn’t get missed?

Changed comment to TODO.

@srekolam
Copy link
Copy Markdown
Contributor

srekolam commented Feb 1, 2022

can we get this reviewed and if okay,merged ?

Copy link
Copy Markdown
Member

@alalazo alalazo left a comment

Choose a reason for hiding this comment

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

Just a couple of questions. Other than that @trws approved, so fine with me to merge.

Comment on lines +56 to +57
"13d3525078fd1c569f7c8ea7fce439b04f6b03814bbe88600c08f95c788e7802",
"13d3525078fd1c569f7c8ea7fce439b04f6b03814bbe88600c08f95c788e7802",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Is this correct that shas are the same?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, the sha (13d3525) stayed the same for 4.3.0 to 4.3.1. 4.5.0 updated to 3d7277fd6.

Comment on lines +67 to +68
"ec6cc4a9c24f098496de3206714dafe9a714f06afacfe21d53a4e6344f9cb4c9",
"ec6cc4a9c24f098496de3206714dafe9a714f06afacfe21d53a4e6344f9cb4c9",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same question here

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Same answer as above. Sha stayed the same from 4.3.0 to 4.3.1.

@alalazo alalazo merged commit 0a595d4 into spack:develop Feb 1, 2022
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Feb 1, 2022
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Feb 8, 2022
EthanS94 pushed a commit to EthanS94/spack that referenced this pull request Feb 17, 2022
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.

4 participants