[llvm-dev] [cfe-dev] Orc Windows C++

Andy Ayers via llvm-dev llvm-dev at lists.llvm.org
Fri Oct 2 11:45:08 PDT 2015

If LLVM is generating the x64 code and you have specified a large code model, you should not see any 32 bit relocations.

So it would be interesting to determine what kind of relocation you are seeing and where it came from.

-----Original Message-----
From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Joshua Gerrard via llvm-dev
Sent: Friday, October 2, 2015 1:18 AM
To: Hayden Livingston <halivingston at gmail.com>
Cc: llvm-dev <llvm-dev at lists.llvm.org>
Subject: Re: [llvm-dev] [cfe-dev] Orc Windows C++

Thanks for the link!
There’s some code there that looks extremely relevant to say the least.

> On 1 Oct 2015, at 19:00, Hayden Livingston <halivingston at gmail.com> wrote:
> Maybe looking at their code might help:
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithu
> b.com%2fdotnet%2fllilc%2fblob%2fdd12743f9cdb5418f1c39b2cd756da1e8396a9
> 22%2flib%2fJit%2fLLILCJit.cpp%23L299&data=01%7c01%7candya%40microsoft.
> com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011d
> b47%7c1&sdata=4LCM5dPAFSQZYdEV2jNoXbtIg79%2foS5%2bB8O2Nl3ZqT4%3d
> On Thu, Oct 1, 2015 at 10:45 AM, David Blaikie via llvm-dev 
> <llvm-dev at lists.llvm.org> wrote:
>> Moving to the LLVM Dev list & cc'ing Lang.
>> On Thu, Oct 1, 2015 at 4:23 AM, Joshua Gerrard via cfe-dev 
>> <cfe-dev at lists.llvm.org> wrote:
>>> Hello folks,
>>> I’m developing an application that uses Orc JIT for C++, which works 
>>> swimmingly on Mac OS X. However, the Windows version has been a 
>>> battle and a half, and it’s now at the point where I need some assistance to progress.
>>> The problem I’m having is “Relocation overflow” (related:
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fllv
>>> m.org%2fbugs%2fshow_bug.cgi%3fid%3d23228%23c8%2c&data=01%7c01%7candy
>>> a%40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=SnxHR5RzKhzNYFDeryATV0MSpqTcjZauHtTG2GTEazA%3d see #8) … so I spoke to some clang developers who focussed on Windows at CppCon last week, and they gave me the following advice:
>>> - Use ELF
>>>    - Using this results in another issue about comdat sections, see here:
>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2froo
>>> t.cern.ch%2fphpBB3%2fviewtopic.php%3ft%3d19808&data=01%7c01%7candya%
>>> 40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f141a
>>> f91ab2d7cd011db47%7c1&sdata=DxCUHFZFW7SxfN6pHlHDfT3yY4DrE5DZTyLCVDWv
>>> 3Yw%3d
>>> - Stick with COFF, but use the large code model
>>>    - No observed difference, seems to be the case because JITDefault 
>>> is being used in the same way as Large, which would make sense
>>>    - According to the clang developers I spoke to, Lang and Andy 
>>> might have an interest in fixing this (would seem likely, as they’re 
>>> the two commenters on the first issue I linked), since it’s better 
>>> to use COFF on Windows than keep trying to work around it
>>> Any ideas?
>>> Thanks in advance!
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org
>>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flist
>>> s.llvm.org%2fcgi-bin%2fmailman%2flistinfo%2fcfe-dev&data=01%7c01%7ca
>>> ndya%40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86
>>> f141af91ab2d7cd011db47%7c1&sdata=9uOfIMd1%2b2DesS3Bne%2f2jkbDpV5REzk
>>> VYj33rujvMGY%3d
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists
>> .llvm.org%2fcgi-bin%2fmailman%2flistinfo%2fllvm-dev&data=01%7c01%7can
>> dya%40microsoft.com%7ce71168aad7ca4c98ee1f08d2cb024bf8%7c72f988bf86f1
>> 41af91ab2d7cd011db47%7c1&sdata=FZAxWxfyZeisom9maEJGCLgK2aboy%2bnneyka
>> 4FPlh%2bE%3d

LLVM Developers mailing list
llvm-dev at lists.llvm.org

More information about the llvm-dev mailing list