diff options
author | Kartik Agaram <vc@akkartik.com> | 2020-06-21 10:59:34 -0700 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2020-06-21 11:06:25 -0700 |
commit | c70beadc7acb5f26c2d63f1ef823a8ed9c720879 (patch) | |
tree | 534893a5e026239ec682c8e0062d10bf4297ae4e /prototypes | |
parent | 19fea2b6a2f6ecfe2279ae4e31f72567131a4423 (diff) | |
download | mu-c70beadc7acb5f26c2d63f1ef823a8ed9c720879.tar.gz |
6562
The new failing test is now passing, and so is this manual test that had been throwing a spurious error: fn foo { var a/eax: int <- copy 0 var b/ebx: int <- copy 0 { var a1/eax: int <- copy 0 var b1/ebx: int <- copy a1 } b <- copy a } However, factorial.mu is still throwing a spurious error. Some history on this commit's fix: When I moved stack-location tracking out of the parsing phase (commit 6116, Mar 10) I thoughtlessly moved block-depth tracking as well. And the reason that happened: I'd somehow gotten by without ever cleaning up vars from a block during parsing. For all my tests, this is a troubling sign that I'm not testing enough. The good news: clean-up-blocks works perfectly during parsing.
Diffstat (limited to 'prototypes')
0 files changed, 0 insertions, 0 deletions