-
Notifications
You must be signed in to change notification settings - Fork 62
[flang][OpenMP] Document do concurent
mapping status and next steps
#100
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
Conversation
Adds a doc to document the current status of `do concurent` mapping, its limitation, and potential next steps.
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 think this looks good as a starting point.
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.
Thank you Kareem for writing this document. It helps quite a bit understanding the current handling of do concurrent
. We just need to make sure to keep it updated as we make changes to it! I just have a couple of suggestions for changes, but just small things.
|
||
### More advanced detection of loop nests | ||
|
||
As pointed out earlier, any intervening code between the headers of 2 nested `do concurrent` loops prevents us currently from detecting this as a loop nest. In some cases this is overly conservative. Therefore, a more flexible detection logic of loop nests needs to be implemented. |
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.
Do you have already any plan in mind to decide where to place the operations that were originally located between the outer and inner loop?
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.
Nothing concrete yet. Stay tuned 😛.
Adds a doc to document the current status of
do concurent
mapping, itslimitation, and potential next steps.
This PR assumes the latest status of #89 is taken into account.