search for: _osabi

Displaying 3 results from an estimated 3 matches for "_osabi".

Did you mean: osabi
2012 Oct 17
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
...CTargetDesc/ARMAsmBackend.cpp index 1ba6ab0..a2c6f7d 100644 --- a/lib/Target/ARM/MCTargetDesc/ARMAsmBackend.cpp +++ b/lib/Target/ARM/MCTargetDesc/ARMAsmBackend.cpp @@ -561,7 +561,10 @@ public: uint8_t OSABI; ELFARMAsmBackend(const Target &T, const StringRef TT, uint8_t _OSABI) - : ARMAsmBackend(T, TT), OSABI(_OSABI) { } + : ARMAsmBackend(T, TT), OSABI(_OSABI) { + // FIXME: Are there versions of ELF-ARM that do not support data-in-code? + HasDataInCodeSupport = true; + } void applyFixup(const MCFixup &Fixup, char *Data, unsigned DataSize,...
2012 Oct 16
2
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
Attached is an example of how to reproduce the issue. It uses a C file that happens to has a bunch of switch statements which are encoded as jump tables, giving us data-in-code. Usage: To build object files with clang via the -integrated-as versus via GCC: $ export NDK_DIR=<my_ndk_dir> $ export LLVM_DIR=<my_llvm_bin_dir> $ make To test that the generated objects contain the same
2013 Sep 25
1
[LLVMdev] arm64 / iOS support
...sFixupValue(const MCAssembler &Asm, IsResolved = false; } - static uint64_t adjustFixupValue(unsigned Kind, uint64_t Value); namespace { +class DarwinAArch64AsmBackend : public AArch64AsmBackend { +public: + DarwinAArch64AsmBackend(const Target &T, const StringRef TT, uint8_t _OSABI) + : AArch64AsmBackend(T, TT) {} + bool mayNeedRelaxation(const MCInst &) const { return false; } + + virtual bool doesSectionRequireSymbols(const MCSection &Section) const { + SectionKind kind = Section.getKind(); + return kind.isDataRel() || kind.isReadOnlyWithRel() || kind.i...