diff options
author | Alon Zakai <azakai@google.com> | 2020-01-22 08:48:53 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-01-22 08:48:53 -0800 |
commit | 474269867c54c7f6031bd6797f4fe96db5783c49 (patch) | |
tree | 891228ae2340de609264c2bd072d6c0d7e7d2c59 /src/shell-interface.h | |
parent | d6ce516017f6ea809babb6d81e5bb791ea94659c (diff) | |
download | binaryen-474269867c54c7f6031bd6797f4fe96db5783c49.tar.gz binaryen-474269867c54c7f6031bd6797f4fe96db5783c49.tar.bz2 binaryen-474269867c54c7f6031bd6797f4fe96db5783c49.zip |
DWARF: Track more function locations (#2604)
DWARF from LLVM can refer to the first byte belonging to the function,
where the size LEB is, or to the first byte after that, where the local
declarations are, or the end opcode, or to one byte past that which is
one byte past the bytes that belong to the function. We aren't sure why
LLVM does this, but track it all for now.
After this all debug line positions are identified. However,
in some cases a debug line refers to one past the end of the
function, which may be an LLVM bug. That location is ambiguous
as it could also be the first byte of the next function (what
made this discovery possible was when this happened to the
last function, after which there is another section).
Diffstat (limited to 'src/shell-interface.h')
0 files changed, 0 insertions, 0 deletions