Hi, I have recently upgraded my project to LLVM 3.6 and I am wondering whether I should have waited for version 3.6.1. With JIT having been officially superseded by MCJIT, I updated my code and got everything working fine on 64-bit Windows, 32-bit/64-bit Linux and OS X, but it's not working properly on 32-bit Windows. Basically, the issue I am having is similar to the one reported in Bug 22963 (https://llvm.org/bugs/show_bug.cgi?id=22963). Everything works fine the very first time I try to compile some code, but if I try to compile some other code, then it will fail as reported in the bug report. I was therefore wondering whether there is a known workaround for this issue? Ideally, I wouldn't have to go back to LLVM 3.5.1. Cheers, Alan. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150401/e3bab1ad/attachment.html>
Thanks for the poke. I fixed the issue in r233819. It'll be in the next point release. On Tue, Mar 31, 2015 at 10:22 PM, Alan Garny <agarny at hellix.com> wrote:> Hi, > > > > I have recently upgraded my project to LLVM 3.6 and I am wondering whether > I should have waited for version 3.6.1… With JIT having been officially > superseded by MCJIT, I updated my code and got everything working fine on > 64-bit Windows, 32-bit/64-bit Linux and OS X, but it’s not working properly > on 32-bit Windows. > > > > Basically, the issue I am having is similar to the one reported in Bug > 22963 (https://llvm.org/bugs/show_bug.cgi?id=22963). Everything works > fine the very first time I try to compile some code, but if I try to > compile some other code, then it will fail as reported in the bug report. > > > > I was therefore wondering whether there is a known workaround for this > issue? Ideally, I wouldn’t have to go back to LLVM 3.5.1… > > > > Cheers, Alan. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150401/b9288f8a/attachment.html>
Thanks a lot Reid. It’s much appreciated. I am going to apply your to my local copy of LLVM 3.6 and see how it goes. Cheers, Alan. From: Reid Kleckner [mailto:rnk at google.com] Sent: 01 April 2015 18:56 To: Alan Garny Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] Workaround for Bug 22963? Thanks for the poke. I fixed the issue in r233819. It'll be in the next point release. On Tue, Mar 31, 2015 at 10:22 PM, Alan Garny <agarny at hellix.com> wrote: Hi, I have recently upgraded my project to LLVM 3.6 and I am wondering whether I should have waited for version 3.6.1… With JIT having been officially superseded by MCJIT, I updated my code and got everything working fine on 64-bit Windows, 32-bit/64-bit Linux and OS X, but it’s not working properly on 32-bit Windows. Basically, the issue I am having is similar to the one reported in Bug 22963 (https://llvm.org/bugs/show_bug.cgi?id=22963). Everything works fine the very first time I try to compile some code, but if I try to compile some other code, then it will fail as reported in the bug report. I was therefore wondering whether there is a known workaround for this issue? Ideally, I wouldn’t have to go back to LLVM 3.5.1… Cheers, Alan. _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150401/6e53f203/attachment.html>
Possibly Parallel Threads
- [LLVMdev] Workaround for Bug 22963?
- [LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
- [LLVMdev] Building LLVM as a shared library using Visual C++ 2010?
- [LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
- [LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013