This is an archive of the discontinued LLVM Phabricator instance.

The second fix of "determination of statements that contain matrix multiplication"
ClosedPublic

Authored by gareevroman on Jun 3 2016, 9:22 AM.

Details

Summary

Fix potential issue related to subtraction from an unsigned 0 in circularShiftOutputDims and check that a parameter of ScheduleTreeOptimizer::isMatrMultPattern contains a correct partial schedule.

Diff Detail

Repository
rL LLVM

Event Timeline

gareevroman updated this revision to Diff 59569.Jun 3 2016, 9:22 AM
gareevroman retitled this revision from to The second fix of "determination of statements that contain matrix multiplication".
gareevroman updated this object.
gareevroman added a subscriber: pollydev.
Meinersbur accepted this revision.Jun 3 2016, 10:06 AM
Meinersbur edited edge metadata.

Thanks for the patch.

You could credit Mehdi Amini for finding the issue in the commit message.

Instead of "The second fix of" in the title try to summarize what it does independently of other commits. Avoids searching for the other commit in the commit list.

If the summary already has the format "<do stuff> and <do stuff>", can you commit those independently? It makes bisecting for finding a corrupting change more precise. In this case it would be
"Fix potential issue related to subtraction from an unsigned 0 in circularShiftOutputDims."
and
"Check that a parameter of ScheduleTreeOptimizer::isMatrMultPattern contains a correct partial schedule. NFC."

You can commit such obvious bugfixes right away.

This revision is now accepted and ready to land.Jun 3 2016, 10:06 AM
grosser edited edge metadata.Jun 3 2016, 10:23 AM

Thanks for your quick reviews. They are perfect.

Thank you for the comment!

Thanks for the patch.

You could credit Mehdi Amini for finding the issue in the commit message.

Yes, I’ve planned to do it.

Instead of "The second fix of" in the title try to summarize what it does independently of other commits. Avoids searching for the other commit in the commit list.

If the summary already has the format "<do stuff> and <do stuff>", can you commit those independently? It makes bisecting for finding a corrupting change more precise. In this case it would be
"Fix potential issue related to subtraction from an unsigned 0 in circularShiftOutputDims."
and
"Check that a parameter of ScheduleTreeOptimizer::isMatrMultPattern contains a correct partial schedule. NFC."

You can commit such obvious bugfixes right away.

OK. I thought that it's already simple.

This revision was automatically updated to reflect the committed changes.