diff options
author | Alon Zakai <azakai@google.com> | 2020-01-22 14:00:25 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-01-22 14:00:25 -0800 |
commit | 60cfc85293c18ca49b25daa4328e5902d4130dae (patch) | |
tree | 5acecde54dd4565dd3a6cce7303c12630d37c8fb /test/control_flow.cpp | |
parent | 70a6817d39fc578def7e91c1abcf31eeb7270135 (diff) | |
download | binaryen-60cfc85293c18ca49b25daa4328e5902d4130dae.tar.gz binaryen-60cfc85293c18ca49b25daa4328e5902d4130dae.tar.bz2 binaryen-60cfc85293c18ca49b25daa4328e5902d4130dae.zip |
DWARF: Update debug_ranges (#2612)
Pretty straightforward given all we have so far.
Note that fannkuch3_manyopts has an example of
a sequence of ranges of which some must be skipped
while others must not, showing we handle that by
skipping the bad ones and updating the remaining. That
is, if that we have a sequence of two (begin, end) spans
[(10, 20),
(30, 40)]
It's possible (10, 20) maps in the new binary to (110, 120)
while (30, 40) was eliminated by the optimizer and we have
nothing valid to map it to. In that case we emit
[(110, 120)]
Diffstat (limited to 'test/control_flow.cpp')
0 files changed, 0 insertions, 0 deletions