Commit 7bcfee1
authored
JIT: Handle possibility of late optimized out async calls (#121502)
If we optimize an async call away after the suspension/resumption code
has been created then the emit locations used for resumption info and
diagnostic info will not be valid. Handle this rare case by just storing
0. The value should not matter as we will never suspend here.
Suspension blocks can be removed in this case, but resumption blocks
cannot as they are referenced by the resumption switch. Ideally we would
model things so that resumption blocks could too be removed in these
cases, but that's not so simple.
Fixes issue reported in
#121298 (comment)1 parent 83496bf commit 7bcfee1
2 files changed
+8
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6774 | 6774 | | |
6775 | 6775 | | |
6776 | 6776 | | |
6777 | | - | |
| 6777 | + | |
6778 | 6778 | | |
6779 | 6779 | | |
6780 | 6780 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8553 | 8553 | | |
8554 | 8554 | | |
8555 | 8555 | | |
8556 | | - | |
| 8556 | + | |
| 8557 | + | |
| 8558 | + | |
8557 | 8559 | | |
8558 | 8560 | | |
8559 | 8561 | | |
8560 | 8562 | | |
8561 | 8563 | | |
8562 | 8564 | | |
8563 | | - | |
| 8565 | + | |
| 8566 | + | |
| 8567 | + | |
| 8568 | + | |
8564 | 8569 | | |
8565 | 8570 | | |
8566 | 8571 | | |
| |||
0 commit comments