search for: a6b3b7d5

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

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

...nced 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 Size: 1058 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/a6b3b7d5/attachment-0001.obj>