This is an archive of the discontinued LLVM Phabricator instance.

[pseudo] Add ambiguity & unparseability metrics to -print-statistics
ClosedPublic

Authored by sammccall on Jul 20 2022, 1:37 PM.

Details

Summary

These can be used to quantify parsing improvements from a change.

Diff Detail

Event Timeline

sammccall created this revision.Jul 20 2022, 1:37 PM
Herald added a project: Restricted Project. · View Herald TranscriptJul 20 2022, 1:37 PM
sammccall requested review of this revision.Jul 20 2022, 1:37 PM
Herald added a project: Restricted Project. · View Herald TranscriptJul 20 2022, 1:37 PM

As mentioned offline, we may want a length-weighted version of the ambiguity metric when prioritizing, but I think this one is easier to understand in isolation. If we end up preferring the weighted version we can change this.

Would it make sense to expose this tool run + statistics as a library. This would help share the code for all the metrics with google3 (as we wanted to keep these metrics in both the places).

This revision was not accepted when it landed; it landed in state Needs Review.Jul 22 2022, 1:35 AM
This revision was automatically updated to reflect the committed changes.

Landed the patch. Will extract this as a library to share this with other continuous evaluation pipeline.