Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Proposal: arbitrary relocations in constant global initializers"
2016 Oct 18
2
Proposal: arbitrary relocations in constant global initializers
To the right list this time.
On Tue, Oct 18, 2016 at 12:43 PM Eric Christopher <echristo at gmail.com>
wrote:
> Hi Peter,
>
> Coming back to his now.
>
>
> IFCC, the previous attempt to teach LLVM to emit jump tables, was removed
> for complicating how functions are emitted, in particular requiring a
> subtarget-specific instruction emitter available in
2016 Oct 07
2
Proposal: arbitrary relocations in constant global initializers
On Fri, Oct 7, 2016 at 12:20 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com
> wrote:
> I've tried implementing some of the alternatives mentioned in this
> thread, and so far I like this syntax the most:
>
> i32 reloc (29, void ()* @f, 3925868544)
> ; 29 = 0x1d = R_ARM_JUMP24
> ; 3925868544 = 0xea000000
>
> Note the zeroes in the relocated data instead of
2016 Oct 07
2
Proposal: arbitrary relocations in constant global initializers
On Fri, Oct 7, 2016 at 1:55 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com>
wrote:
> On Fri, Oct 7, 2016 at 1:22 PM, Peter Collingbourne <peter at pcc.me.uk>
> wrote:
> > On Fri, Oct 7, 2016 at 12:20 PM, Evgenii Stepanov
> > <eugeni.stepanov at gmail.com> wrote:
> >>
> >> I've tried implementing some of the alternatives mentioned in
2016 Oct 07
2
Proposal: arbitrary relocations in constant global initializers
On Fri, Oct 7, 2016 at 2:48 PM, Evgenii Stepanov <eugeni.stepanov at gmail.com>
wrote:
> On Fri, Oct 7, 2016 at 2:28 PM, Peter Collingbourne <peter at pcc.me.uk>
> wrote:
> > On Fri, Oct 7, 2016 at 1:55 PM, Evgenii Stepanov <
> eugeni.stepanov at gmail.com>
> > wrote:
> >>
> >> On Fri, Oct 7, 2016 at 1:22 PM, Peter Collingbourne <peter
2015 Aug 26
2
Proposal: arbitrary relocations in constant global initializers
On Wed, Aug 26, 2015 at 11:49:46AM -0400, Rafael Espíndola wrote:
> This is pr10368.
>
> Do we really need to support hard coded relocation numbers? Looks like
> the examples above have a representation as constant expressions:
>
> (sub (add (ptrtoint @foo) 0xeafffffe) cur_pos)
>
> no?
I'm not sure if this would be sufficient. The R_ARM_JUMP24 relocation
on ARM
2015 Aug 26
2
Proposal: arbitrary relocations in constant global initializers
On Wed, Aug 26, 2015 at 03:53:33PM -0400, Rafael Espíndola wrote:
> > I'm not sure if this would be sufficient. The R_ARM_JUMP24 relocation
> > on ARM has specific semantics to implement ARM/Thumb interworking; see
> > http://infocenter.arm.com/help/topic/com.arm.doc.ihi0044e/IHI0044E_aaelf.pdf
> > Note that R_ARM_CALL has the same operation but different semantics.
2015 Jan 26
2
[LLVMdev] [llvm] r188726 - Adding PIC support for ELF on x86_64 platforms
Hi Lang,
Yeah, I remember this case. Basically what’s happening is that there are relocations for ELF on x86 that use a value that is present in the object image as part of the calculation for the final value that goes in the same location. If you ever find yourself applying relocations for a second time (for instance, because the loaded object location is remapped for out-of-proc execution)
2012 Aug 03
1
[LLVMdev] llvm-objdump does not give information about all relocations
Hi,
We are trying to use LLVM API to programmatically obtain a list of
relocations in an ELF file. The way we are doing this is exactly as
llvm-objdump does it: we are iterating through sections and in each
section we are iterating over relocations (see PrintRelocations()
function at https://llvm.org/svn/llvm-project/llvm/trunk/tools/llvm-objdump/llvm-objdump.cpp).
However, it does not give us
2012 Mar 23
0
[LLVMdev] Sorting relocation entries
Hi Jim,
Thanks for reviewing the patch.
I couldn't get rid of STLExtras.h, but other than that, I followed all
the suggestions in your email.
Please let me know if you notice anything else that needs fixing.
On Thu, Mar 22, 2012 at 4:42 PM, Jim Grosbach <grosbach at apple.com> wrote:
> Hi Akira,
>
> This is looking good. Some specific comments on the details below.
>
>
2012 Mar 23
1
[LLVMdev] Sorting relocation entries
Hi Akira,
Just two very minor things that I missed the first time around.
1. The 'fixup" member of ELFRelocation entry should be "Fixup" instead.
2. Since we're always passing in a non-NULL fixup, that should probably be a reference, not a pointer.
Good for commit with those tweaks.
Thanks!
-Jim
On Mar 23, 2012, at 1:07 PM, Akira Hatanaka wrote:
> Hi Jim,
>
2012 Mar 22
2
[LLVMdev] Sorting relocation entries
Hi Akira,
This is looking good. Some specific comments on the details below.
Thanks!
Jim
> diff --git a/include/llvm/MC/MCELFObjectWriter.h b/include/llvm/MC/MCELFObjectWriter.h
> index 6e9f5d8..220ecd0 100644
> --- a/include/llvm/MC/MCELFObjectWriter.h
> +++ b/include/llvm/MC/MCELFObjectWriter.h
> @@ -13,6 +13,7 @@
> #include "llvm/MC/MCObjectWriter.h"
>
2014 Feb 26
2
[LLVMdev] [lld] Relocation reading refactoring
Hi Shankar,
On Tue, Feb 12, 2013 at 10:46 PM, Shankar Easwaran
<shankare at codeaurora.org> wrote:
> Author: shankare
> Date: Tue Feb 12 12:46:53 2013
> New Revision: 174990
>
> URL: http://llvm.org/viewvc/llvm-project?rev=174990&view=rev
[...]
> ELFDefinedAtom<ELFT> *createDefinedAtomAndAssignRelocations(
> StringRef symbolName, StringRef
2020 Aug 05
1
Switch to ld.bfd tombstone behavior by default
On Wed, Aug 5, 2020 at 12:50 PM Fāng-ruì Sòng <maskray at google.com> wrote:
> On Wed, Aug 5, 2020 at 12:32 PM Eric Christopher <echristo at gmail.com>
> wrote:
> >
> > Honestly even though I do understand the debug information I'm with you
> and one reason why I'm pushing for the same reset that you are. There are a
> lot of threads, it's fairly
2016 Feb 03
2
lld dynamic relocation creation issue
Hi all,
Working on lld aarch64 support I came across an issue where I am not sure which
would be best design approach to solve.
The aarch64 R_AARCH64_ABS64 relocation for PIC/PIE build requires a dynamic
relocation (R_AARCH64_RELATIVE) with the value set as the addend of the
relocation. For instance, when linking the crtbeginS.o which contains:
Relocation section '.rela.init_array' at
2020 Aug 05
2
Switch to ld.bfd tombstone behavior by default
Can we please just revert back to what we had before until the
discussion about the desired behaviour and how to get there reaches a
conclusion?
In particular, I would like to merge that revert to the 11.x branch.
At this point in the release process, I'm not keen on taking any patch
that changes the behavior to something that hasn't been well tested
from sitting in trunk for a while.
On
2015 Aug 05
2
[LLVMdev] Cc llvmdev: Re: llvm bpf debug info. Re: [RFC PATCH v4 3/3] bpf: Introduce function for outputing data to perf event
Hi, Alexei
On 2015/7/30 1:13, Alexei Starovoitov wrote:
> On 7/29/15 2:38 AM, He Kuang wrote:
>> Hi, Alexei
>>
>> On 2015/7/28 10:18, Alexei Starovoitov wrote:
>>> On 7/25/15 3:04 AM, He Kuang wrote:
>>>> I noticed that for 64-bit elf format, the reloc sections have
>>>> 'Addend' in the entry, but there's no 'Addend' info
2012 Sep 21
1
[LLVMdev] relocation visitor
Currently llvm-dwarfdump isn't very useful on ELF .o files because it
doesn't apply relocations.
nlewycky at ducttape:~$ llvm-dwarfdump helloworld.o | grep debug_str\\[
0x0000000c: DW_AT_producer [DW_FORM_strp] ( .debug_str[0x00000000] =
"clang version 3.2 (trunk 163034)")
0x00000012: DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000000] = "clang
version 3.2 (trunk
2020 Aug 05
2
Switch to ld.bfd tombstone behavior by default
Honestly even though I do understand the debug information I'm with you and
one reason why I'm pushing for the same reset that you are. There are a lot
of threads, it's fairly confusing what has been done where and other than
some fairly widespread breakage among early users of lld (i.e. a short time
from commit to use) it's unclear what the plan is to roll this out
effectively
2018 Jan 10
3
llvm-mc assembler, GNU as, and pc-relative branches for Arm/AArch64/Mips
# Summary
As a consequence of comparing the RISC-V LLVM MC assembler to the RISC-V GNU
assembler I've noticed that a number of targets have quite different handling
for pc-relative jumps/branches with immediate integer operands in llvm-mc vs
GNU as. I'll admit that this isn't likely to occur in hand-written code (as
you'd almost always prefer to use a label), but thought it was
2012 Feb 09
1
[LLVMdev] Questions on MachineFunctionPass and relaxation of pcrel calls (ARM/thumb2)
While implementing a MachineFunctionPass that runs as part of the
ARMTargetMachine::addPreEmitPass(), I've run into a problem.
This particular MFP can drastically increase the size (in MachineInstr
count) of the MachineFunction that it processes, so much so that
there is a real danger of pcrel calls and branches that use immediate
offsets to not be sufficient.
A naive test confirmed that