This is an archive of the discontinued LLVM Phabricator instance.

[AMDGPU] Regen checks for no-remat-indirect-mov
ClosedPublic

Authored by Joe_Nash on Mar 15 2022, 10:34 AM.

Details

Summary

NFC. Hasn't been updated since the update script started adding
check-next.

Diff Detail

Event Timeline

Joe_Nash created this revision.Mar 15 2022, 10:34 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 15 2022, 10:34 AM
Herald added subscribers: kerbowa, t-tye, tpr and 4 others. · View Herald Transcript
Joe_Nash requested review of this revision.Mar 15 2022, 10:34 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 15 2022, 10:34 AM
arsenm accepted this revision.Mar 15 2022, 10:36 AM
This revision is now accepted and ready to land.Mar 15 2022, 10:36 AM

@arsenm PTAL, I realize the commit message was misleading. It appears like something changed and the checks weren't regenerated. Could be related to @foad patch cce93b339724a34928f0630fa8ed6b09b4ba753b , since that's when the 2nd check line was added.

@arsenm PTAL, I realize the commit message was misleading. It appears like something changed and the checks weren't regenerated. Could be related to @foad patch cce93b339724a34928f0630fa8ed6b09b4ba753b , since that's when the 2nd check line was added.

I'd guess this is related to update_mir_test_checks not understanding what to do when the output is identical between run lines

@arsenm PTAL, I realize the commit message was misleading. It appears like something changed and the checks weren't regenerated. Could be related to @foad patch cce93b339724a34928f0630fa8ed6b09b4ba753b , since that's when the 2nd check line was added.

I'd guess this is related to update_mir_test_checks not understanding what to do when the output is identical between run lines

Ok that makes sense, I both lines are actually identical. Thanks

This revision was landed with ongoing or failed builds.Mar 15 2022, 10:56 AM
This revision was automatically updated to reflect the committed changes.

@arsenm PTAL, I realize the commit message was misleading. It appears like something changed and the checks weren't regenerated. Could be related to @foad patch cce93b339724a34928f0630fa8ed6b09b4ba753b , since that's when the 2nd check line was added.

I'd guess this is related to update_mir_test_checks not understanding what to do when the output is identical between run lines

Ok that makes sense, I both lines are actually identical. Thanks

In that case you should comment out the second run line, regenerate, and re-add the second line. It's an annoying workaround. update_mir_test_checks should be fixed to behave like update_llc_test_checks where it commons individual functions with a shared prefix

@arsenm PTAL, I realize the commit message was misleading. It appears like something changed and the checks weren't regenerated. Could be related to @foad patch cce93b339724a34928f0630fa8ed6b09b4ba753b , since that's when the 2nd check line was added.

I'd guess this is related to update_mir_test_checks not understanding what to do when the output is identical between run lines

Ok that makes sense, I both lines are actually identical. Thanks

In that case you should comment out the second run line, regenerate, and re-add the second line. It's an annoying workaround. update_mir_test_checks should be fixed to behave like update_llc_test_checks where it commons individual functions with a shared prefix

Done 687d20de7ffc69dd4ecdb9808aeb6d3cffcf3871