Displaying 2 results from an estimated 2 matches for "ek_blockaddress".
2016 Jul 29
0
PIC preferred too strongly, even at CodeModel::Large?
...> movslq (%rax,%rdi,4), %rsi
> addq %rax, %rsi
> jmpq *%rsi
>
Ah; I guess I actually should have spotted that.
See
https://github.com/llvm-mirror/llvm/blob/f79c57a412cf8ba35884c1d4e011e07baad334d9/lib/CodeGen/SelectionDAG/TargetLowering.cpp#L281
. I think you can just force it to use EK_BlockAddress for the large code
model.
> >> Second, is it okay to
> >> silently fold into Reloc::PIC_ in this case and leave the user with
> >> sporadic crashes?
> >
> >
> > Large code model and PIC should be compatible.
>
> Technically, yes. My understanding...
2016 Jul 29
2
PIC preferred too strongly, even at CodeModel::Large?
Eli Friedman wrote:
> On Thu, Jul 28, 2016 at 6:13 PM, Ramkumar Ramachandra via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> We were just debugging a sporadic crash the other day, when we noticed
>> that RIP-relative addressing was being used in a JumpTable, even when
>> code and data were well over 4G apart. This is confusing, because we
>> picked