search for: hasrelocationaddend

Hi Shankar, > Does LLVM emit rel/rela relocations with ARM ? I believe we emit .rel for (32-bit) ARM. Hard-coded in ARMELFObjectWriter.cpp (“HasRelocationAddend”). It seems to be what most toolchains have settled on. AArch64 is .rela always in LLVM, in case it matters. > Any tests ? Well there are tests of what we do, but obviously not of the full scope of functionality permitted by the ABI. Cheers. Tim. -------------- next part -------------- A non...

On 3 May 2017 at 08:01, Rafael Avila de Espindola via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Can you provide a .s file that shows the difference? I managed to reproduce it by compiling 'char *var = "whatever";' in debug mode (so clang -target arm-none-eabi tmp.c -g"). Direct compile leaves no assembler-local strings, but for some reason going via -S does.

Hi, I was looking at the ARM ABI docs(http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf) and they mention. "A binary file may use REL or RELA relocations or a mixture of the two (but multiple relocations for the same address must use only one type)." Does LLVM emit rel/rela relocations with ARM ? Any tests ? Thanks Shankar Easwaran -- Qualcomm

Hi all, I have reached the relocation phase of my backend implementation and I'm having some trouble. The LLVM code I'm trying to compile is this: %struct.Date = type { i32, i32, i32 } @date = global %struct.Date { i32 2012, i32 10, i32 120000 }, align 4 ; Function Attrs: nounwind define i32 @foo() #0 { %1 = load i32, i32* getelementptr inbounds (%struct.Date, %struct.Date* @date, i32

...working on this. High level comments: (1) The order of patches is odd, to me. It would be great to start by adding the AsmParser support, then the MCStreamer support, so that we can have test cases in the 'llvm-mc cat' mode, where it just parses and prints out again. On 0001: - What is hasRelocationAddend? It doesn't seem to be needed to me, and I'm not sure why it would be. If this is a private detail to ELF, it shouldn't go in TargetAsmBackend, but rather be an argument to the object writer constructor. - Feel free to submit a patch to split out ELFX86_{32,64}AsmBackend, if you want m...

Hi guys, attached are a couple of work in progress patches for ELF support in the MC module. I'm sending this email to gather some general feedback on the code. Applying these patches doesn't get you a fully working llvm-mc that understands ELF; it's just the ground work. I've got a couple more small patches that fixup some places that assume Mach-O object format which I'll

...> > the difference comes from ELFObjectWriter::shouldRelocateWithSymbol. In > particular > > // It looks like gold has a bug (http://sourceware.org/PR16794) and can > // only handle section relocations to mergeable sections if using RELA. > if (!hasRelocationAddend()) > return true; > > If I remove that we produce a relocation with the section, as does > gas. The gold bug has not been fixed :-( > > Cheers, > Rafael >

...in a section starting with ".rela" puts the offset in with the relocation itself. IMO it's simpler and neater, but it makes the object file slightly bigger. If I was designing a backend and had the freedom, it's what I'd choose to do. If you want to change it you set the "HasRelocationAddend" variable to true in your XYZELFObjectWriter. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190313/6da7c042/attachment-0001.html>