search for: jumptable_bug

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

PIC preferred too strongly, even at CodeModel::Large?
2016 Jul 29
0
PIC preferred too strongly, even at CodeModel::Large?
On Thu, Jul 28, 2016 at 6:13 PM, Ramkumar Ramachandra via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, > > 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 CodeModel::Large, and expected this to
PIC preferred too strongly, even at CodeModel::Large?
2016 Jul 29
4
PIC preferred too strongly, even at CodeModel::Large?
Hi, 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 CodeModel::Large, and expected this to be taken care of. Isn't that what gcc would do given a Large CodeModel? The default Relocation Model, Reloc::Default, folds into
PIC preferred too strongly, even at CodeModel::Large?
2016 Jul 29
2
PIC preferred too strongly, even at CodeModel::Large?
...at exactly are you planning to do with an ELF object file on OS X? I forgot to mention: we're JIT'ting. In any case, isOSDarwin() isn't influenced by an extra "-elf" to the target triple. Ram -------------- next part -------------- A non-text attachment was scrubbed... Name: jumptable_bug.ll Type: application/octet-stream Size: 633 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/a6b3b7d5/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: jumptable_bug.s Type: application/octet-stream...