search for: osabi

...command line and the setting of ABIname in MCTargetOptions to where an instance of a subclass of MCELFObjectTargetWriter is created. I looked at the approach taken by both Mips and X86 for implementing ILP32 and neither seems applicable. For x86 x32, there is the combination of IsELF64 == false and OSABI == EM_X86_64, but that doesn't seem applicable, as the ELF e_machine field is the same for the existing and the new ABI. For Mips N32, code and state in MCELFObjectTargetWriter seems to take care of mapping the relocation values and the ELF e_flags bit EF_MIPS_ABI_ON32 is set. I'm trying to...

...at least lets me improve matters. By the way, you'll find that some paths through clang use the default constructor of MCTargetOptions and therefore neglect to set MCTargetOptions::ABIName. I was planning to fix this once I had the backend side of things working. > Should I make up a new OSABI enum value? Do some kind of manipulation of the Triple environment field to set it based upon the value of "-mabi="? Both of those approaches would work and are similar to Debian's concept of Multiarch Tuples. My original TargetTuple solution was somewhat similar in principle but...

...t MCExpr *Value) { diff --git a/lib/Target/ARM/MCTargetDesc/ARMAsmBackend.cpp b/lib/Target/ARM/MCTargetDesc/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? + HasDataInCodeSupp...

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

...ironment for x86-64 target to tell X32 psABI from LP64 psABI (i.e. the original x86-64 ABI). The patch to clang adds '-mx32' option to generate x32 binaries as well as support calling convention changes due to pointer size reduction. Please commit the patch if it seems acceptable. This new osABI, X32 psABI, allows programs to run in the 64-bit mode but only using 32-bit pointers. Though, programs will be limited to 4GB virtual address space (not all application requires more than 4GB), X32 psABI helps reduce memory footprint and file size and allow them run faster. The following are statis...

...lines are the same. - Add "-ggdb3 -O0" to GCCWARN in mk/devel.mk. - I use the following commands in my .gdbinit to load the symbols of the main file and set the right architecture. file bios/core/lpxelinux.elf target remote localhost:1234 #set architecture i8086 set architecture i386 set osabi none Depending whether you're debugging 16 bits or 32 bits code, you will need to set the architecture accordingly. You can switch on the fly if the disass command decode the instructions incorrectly. (At least or worked for me, I use a 32 bits OS.) Note that the order is quite important as gd...

On Wed, Jan 13, 2016 at 01:22:17AM +0100, Celelibi wrote: > 2016-01-12 22:21 UTC+01:00, Tal Lubko: > > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller wrote: > >> > >> Yes, you can print debug-output from custom builds. > >> > > > > Regarding my other question (debugging). > > I know it is possible to use prints for debugging. > > I

...ironment for x86-64 target to tell X32 psABI from LP64 psABI (i.e. the original x86-64 ABI). The patch to clang adds '-mx32' option to generate x32 binaries as well as support calling convention changes due to pointer size reduction. Please commit the patch if it seems acceptable. This new osABI, X32 psABI, allows programs to run in the 64-bit mode but only using 32-bit pointers. Though, programs will be limited to 4GB virtual address space (not all application requires more than 4GB), X32 psABI helps reduce memory footprint and file size and allow them run faster. The following are statis...

...w versions of those files. * The install target runs install -s to strip the installed programs. However this runs strip(1) on the program, not $STRIP. This matters when cross-compiling where the system strip might not correctly handle the programs. This happened to me where it changed the OSABI ELF header value. The build system should instead respect the user CFLAGS and install a non-stripped version if that's what's built. I hear some autoconf projects a install-strip target (though I haven't checked). It's probably desirable to change the default from --enab...

...FixupValue(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...