{"push_id":591011270,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"7f7e33b270722cbe57094630c731d87509b85fbe","before":"36c934997a7a5097036edab0b5388defb0a53a53","commits":[{"sha":"dc3a2df8dd59336db8758472dc0f24f8030fd861","author":{"email":"a0eed57aaedf007a763cbac2dd65f90f9fe7ec18@gmail.com","name":"Elliot Ronaghan"},"message":"Cleanup how leader and standalone iters are marked for inlining\n\nAdds helper routines that check if a function is a specific type of iterator\n(leader, standalone, follower.) These functions are then used to find leader\nand standalone iterators and mark them for inlining. This separates the logic\nof checking if a fn is a particular iterator from whatever you want to do with\nthe iterator.\n\nThis also moves the standalone marking up with the leader marking.\n\nThis is a peeled off commit from my vectorize-follower-loops patch (which also\nadds and uses an isFollowerIterator function())","distinct":true,"url":"https://api.github.com/repos/chapel-lang/chapel/commits/dc3a2df8dd59336db8758472dc0f24f8030fd861"},{"sha":"dd0954c177b221c3a54d4b0396ddc2f7a3df9304","author":{"email":"a0eed57aaedf007a763cbac2dd65f90f9fe7ec18@gmail.com","name":"Elliot Ronaghan"},"message":"Bug fix: Stash a pristine copy of standalone iters like we do for leaders\n\nDuring review Vass noticed that we should also be stashing a pristine copy of\nthe standalone iters.\n\nA better description from Vass:\n\"\nWith the introduction of standalone iterators, the forall intent\nmachinery has been extended to apply to them, too. Standalone iterators\nare treated much like leader iterators for forall intents. (The function\nnames and comments in implementForallIntents.cpp are still heavy in\nleader-follower terminology - for historical reasons.)\n\nThis change fixes an omission in the above - we need to \"stash pristine\ncopies\" of standalone iterators just like we do leader iterators. The\nomission has not caused us trouble yet perhaps because we have not used\nstandalone iterators in some ways that we have leaders.\n\"","distinct":true,"url":"https://api.github.com/repos/chapel-lang/chapel/commits/dd0954c177b221c3a54d4b0396ddc2f7a3df9304"},{"sha":"7f7e33b270722cbe57094630c731d87509b85fbe","author":{"email":"a0eed57aaedf007a763cbac2dd65f90f9fe7ec18@gmail.com","name":"Elliot Ronaghan"},"message":"Merge pull request #1448 from ronawho/cleanup-iter-inline-marking\n\nBug fix and cleanup for leader/standalone iter marking during resolution\r\n\r\n[reviewed by @vasslitvinov and @daviditen]\r\n\r\nBug fix and cleanup for leader/standalone iter marking during resolution\r\n\r\nCleans up how leader and standalone iterators are marked for inlining during\r\nfunction resolution and fixes a bug where a pristine copy of the standalone\r\niterator (required for forall intents) was not being stashed.\r\n\r\nAdds helper routines that check if a function is a specific type of iterator\r\n(leader, standalone, follower.) These functions are then used to find leader\r\nand standalone iterators and mark them for inlining. This separates the logic\r\nof checking if a fn is a particular iterator from whatever you want to do with\r\nthe iterator.\r\n\r\nThis also moves the standalone marking up with the leader marking.\r\n\r\nThis is a peeled off commit from my vectorize-follower-loops patch (which also\r\nadds and uses an isFollowerIterator function())\r\n\r\n\r\nDuring review Vass noticed that we should also be stashing a pristine copy of\r\nthe standalone iterator.\r\n\r\nA better description from Vass:\r\n\"\r\nWith the introduction of standalone iterators, the forall intent\r\nmachinery has been extended to apply to them, too. Standalone iterators\r\nare treated much like leader iterators for forall intents. (The function\r\nnames and comments in implementForallIntents.cpp are still heavy in\r\nleader-follower terminology - for historical reasons.)\r\n\r\nThis change fixes an omission in the above - we need to \"stash pristine\r\ncopies\" of standalone iterators just like we do leader iterators. The\r\nomission has not caused us trouble yet perhaps because we have not used\r\nstandalone iterators in some ways that we have leaders.\r\n\"","distinct":true,"url":"https://api.github.com/repos/chapel-lang/chapel/commits/7f7e33b270722cbe57094630c731d87509b85fbe"}]}