These relocations are used in linux kernel.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
I think we can either implement or error out on these relocations, I personally don't care as implementing this relocations is literally 3 lines of code, but wait for a second opinion.
What I'm most worried about is that we should never produce a broken output given valid input, we should emit a diagnostic and exit.
Somewhat orthogonal to this patch, but I think we need to modify X86TargetInfo::relocateOne so that we explicitly list relocation types that we understand and error out other relocations.
ELF/Target.cpp | ||
---|---|---|
493 ↗ | (On Diff #85589) | No such thing like a one byte little endian value as the endianness is inherently a concept when you have more than one byte, so don't use read<>. That's why we don't have read8{be,le}. Just dereference the uint8_t pointer. |
- Addressed review comments.
ELF/Target.cpp | ||
---|---|---|
493 ↗ | (On Diff #85589) | Yep. Not sure why I wrote in that way. |
lld/trunk/ELF/Target.cpp | ||
---|---|---|
518 | Do you need a cast? |
Do you need a cast?