diff options
| author | Kartik Agaram <vc@akkartik.com> | 2020-10-06 00:36:28 -0700 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2020-10-06 00:36:28 -0700 |
| commit | ce094a5d827b82c48eb76b1b4c04cf899219c33b (patch) | |
| tree | 5fe3a3ef14e3d7de3b291273378935500393ea80 /305keyboard.subx | |
| parent | e41bc160a0dfee0c38ecf20b20ddaf7e6f3da408 (diff) | |
| download | mu-ce094a5d827b82c48eb76b1b4c04cf899219c33b.tar.gz | |
6968
Snapshot that requires a check in the Mu compiler. Currently I don't spill a register if it could possibly be over-written by a function output within. However, find-in-call-path is a good example of where this constraint is too lenient and results in unsafe code. The variable `curr` gets clobbered during loop update by the variable `match?`. What's the answer? Perhaps we should ban all conditional updates to function outputs? That'd be dashed inconvenient.
Diffstat (limited to '305keyboard.subx')
0 files changed, 0 insertions, 0 deletions