https://bugs.llvm.org/show_bug.cgi?id=48827
Bug ID: 48827
Summary: older versions of wasm-ld crashes when when given
object files built with llvm trunk
Product: lld
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: wasm
Assignee: unassignedb...@nondot.org
Reporter: s...@chromium.org
CC: llvm-bugs@lists.llvm.org, s...@chromium.org
We ran into issues where object files built with trunk version llvm were
causing crashes in older versions of wasm-ld.
I believe that this change added a new symbol type to pretty much all object
files which causes older versions of wasm-ld to crash:
https://reviews.llvm.org/D92215
Clearly we need to be able add new symbol types and relocations types I think
we can take a couple of measures here to make things smoother:
1. Report readable errors rather than crashing when new symbol types or
relocation types are added.
2. In this particular case we should avoid using this new symbol type unless we
truly need it. i.e. we should revisit the discussion around whether to use a
table symbol for the default call_indirect table.
WDYT andy? I can take a look at (1) but thats the easy bit. Revisiting (2)
could be trickier? I guess it will make the code less clean for longer but
avoiding breaking changes to the object format is also very compelling.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
