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

Add all remaining prif interfaces #48

Merged
merged 22 commits into from
Dec 19, 2023
Merged

Add all remaining prif interfaces #48

merged 22 commits into from
Dec 19, 2023

Conversation

ktras
Copy link
Collaborator

@ktras ktras commented Dec 18, 2023

Add all remaining prif interfaces based on design doc revision 0.2

ktras added 20 commits December 15, 2023 16:40
more than just a definition for `team_type`, it contains interfaces
for team related statements and procedures.
and `prif_deallocate_non_symmetric` in `allocation_m`.
`prif_event_wait`, and `prif_event_query`.
`prif_set_context_data`, `prif_get_context_data`,
`prif_base_pointer`, and `prif_local_data_size`.
`prif_put_strided`, `prif_put_raw`, `prif_put_raw_strided`,
`prif_get`, `prif_get_raw`, and `prif_get_raw_strided`.
@ktras ktras marked this pull request as ready for review December 18, 2023 19:40
Copy link
Member

@bonachea bonachea left a comment

Choose a reason for hiding this comment

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

Overall LGTM.

I did NOT attempt to exhaustively compare all the subroutine signatures for spec conformance, although that's something that eventually needs to be audited, and ideally supported with test code that ensures calls compile as intended.

src/prif.f90 Show resolved Hide resolved
Copy link
Member

@everythingfunctional everythingfunctional left a comment

Choose a reason for hiding this comment

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

A did a brief once-over and nothing jumps out. LGTM

@ktras ktras requested a review from bonachea December 19, 2023 02:13
Copy link
Member

@bonachea bonachea left a comment

Choose a reason for hiding this comment

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

Removing pure from functions internal to caffeine is probably overkill, but I have no specific objection.

The important part is to match the specified prif_ interfaces at the top.

@ktras
Copy link
Collaborator Author

ktras commented Dec 19, 2023

Removing pure from functions internal to caffeine is probably overkill, but I have no specific objection.

The important part is to match the specified prif_ interfaces at the top.

@bonachea, I agree. I only removed pure from functions that I had to based on the cascading affects of pure being removed from some of the prif_ interfaces that called other pure functions and no longer can. Thanks for the review!

@ktras ktras merged commit e434690 into main Dec 19, 2023
6 checks passed
@ktras ktras deleted the add-all-prif-interfaces branch December 19, 2023 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants