[Work in progress] Check debug information in CmmLint
Changes PlannedPublicDraft

Authored by niteria on Apr 4 2018, 5:23 AM.

Details

Reviewers
bgamari
simonmar
Trac Issues
#15000
Summary

This is still work in progress, I'm submitting it for early feedback and
to be able to refer to this on tickets.

The new Note [Lint Unwind strategy] explains the purpose of this.

This currently triggers, I'm investigating the violations it detects.

Test Plan

todo
It detects the root cause of Trac #14999 and succeeds after the fix from Trac #14999 comment:2

niteria created this revision.Apr 4 2018, 5:23 AM
niteria edited the test plan for this revision. (Show Details)Apr 4 2018, 5:25 AM
niteria updated this revision to Diff 15925.Apr 4 2018, 5:45 AM

start over when Sp updated in a way we don't understand

This looks useful, but it makes me wonder whether we should generate the unwinding info automatically, so it wouldn't be possible to get it wrong. (I'm sure there must be something wrong with this idea)

This looks useful, but it makes me wonder whether we should generate the unwinding info automatically, so it wouldn't be possible to get it wrong. (I'm sure there must be something wrong with this idea)

Do you mean generate unwinding information automatically in the primop implementations? Of course, for C-- produced from STG it is already generated automatically.

Harbormaster returned this revision to the author for changes because remote builds failed.May 3 2018, 2:30 PM