-
Notifications
You must be signed in to change notification settings - Fork 129
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
Cherry-picked a handful of intrinsic related commits out of multi_sdfg
branch.
#1728
Conversation
multi_sdfg
branch that are 1) chrnologically first, 2) fairly indepdent and touches a small amount of files, and 3) thematically fit together.multi_sdfg
branch that are 1) chrnologically early, 2) fairly indepdent and touches a small amount of files, and 3) thematically fit together.
multi_sdfg
branch that are 1) chrnologically early, 2) fairly indepdent and touches a small amount of files, and 3) thematically fit together.multi_sdfg
branch that are 1) chrnologically early, 2) fairly indepdent and touches a small number of files, and 3) thematically fit together.
multi_sdfg
branch that are 1) chrnologically early, 2) fairly indepdent and touches a small number of files, and 3) thematically fit together.multi_sdfg
branch that 1) are chrnologically early, 2) fairly indepdent and touch a small number of files, and 3) thematically fit together.
multi_sdfg
branch that 1) are chrnologically early, 2) fairly indepdent and touch a small number of files, and 3) thematically fit together.multi_sdfg
branch that 1) are chrnologically early, 2) fairly independent and touch a small number of files, and 3) thematically fit together.
multi_sdfg
branch that 1) are chrnologically early, 2) fairly independent and touch a small number of files, and 3) thematically fit together.multi_sdfg
branch.
5d22609
to
4cf4ebf
Compare
Previously, we didn't extract function calls that appear in function arguments. Now we can support that. To that end, we have to declare extracted calls in reverse order - first process arguments, then the main call.
fortran program that passes under `gfortran -Wall`.
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.
LGTM!
@pratyai One more issue: some of the test files might have commented out test function calls; it should be a leftover of prior work. Can you please verify that tests still run after enabling them again? |
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.
One more issue: some of the test files might have commented out test function calls; it should be a leftover of prior work. Can you please verify that tests still run after enabling them again?
8e05082
to
3488c58
Compare
Done. |
These commits:
This is a follow-up on the discussion about incrementally moving the stable features from
multi_sdfg
branch intomain
. All of the commits are cherry-picked to preserve the history and to have easy fast-forwarding of themulti_sdfg
branch.Some commits had to be slightly modified to resolve the merge conflicts during cherry-picking, but otherwise they are left as-is.