This is an archive of the discontinued LLVM Phabricator instance.

Don't print uselistorder in --print-changed
ClosedPublic

Authored by aeubanks on Oct 6 2021, 4:52 PM.

Details

Summary

Using uselistorders is fairly niche, it shouldn't be on by default and mostly just clutters the output.

Diff Detail

Event Timeline

aeubanks created this revision.Oct 6 2021, 4:52 PM
aeubanks requested review of this revision.Oct 6 2021, 4:52 PM
Herald added a project: Restricted Project. · View Herald TranscriptOct 6 2021, 4:52 PM
jamieschmeiser requested changes to this revision.Oct 7 2021, 7:40 AM

As I recall, I added this in based on comments in the review and I am fine with removing it. However, the parameter to unWrapAndPrint was added to preserve existing function and if this is removed, then the parameter should also be removed as it will always be false. The parameter can be dropped from the call to print also, as it defaults to false.

This revision now requires changes to proceed.Oct 7 2021, 7:40 AM
aeubanks updated this revision to Diff 377899.Oct 7 2021, 10:21 AM

address comments

ychen added a comment.Oct 7 2021, 10:34 AM

I was suggesting this to catch non-determinism issues like the one D64866 fixed. Sounds good to me to make it off by default. Any way to make it opt-in? Making it part of API (add a field to PrintPassOptions) would be the best but it could be a follow-up patch with a FIXME added to this patch.

I was suggesting this to catch non-determinism issues like the one D64866 fixed. Sounds good to me to make it off by default. Any way to make it opt-in? Making it part of API (add a field to PrintPassOptions) would be the best but it could be a follow-up patch with a FIXME added to this patch.

Yeah, adding it as a separate flag sounds good if anybody needs it

jamieschmeiser accepted this revision.Oct 7 2021, 11:48 AM

LGTM, thanks

This revision is now accepted and ready to land.Oct 7 2021, 11:48 AM
This revision was automatically updated to reflect the committed changes.