3.5 was already released, and we only merge bug fixes to release branches. Caio, do you really need it on 3.5 specifically or are you just asking if folks are interested to get it into the trunk? - Hans On Mon, Oct 27, 2014 at 3:33 AM, Yaron Keren <yaron.keren at gmail.com> wrote:> +Hans > > Caio, even if this patch does not go into 3.5, maybe you'd like to post it > on llvm-commits so it will be available publicly and not lost. > > Yaron > > > 2014-10-27 12:16 GMT+02:00 Caio Souza Oliveira > <caio.oliveira at eldorado.org.br>: >> >> Hello there! >> >> I’m intending to port LLVM old JIT API for PPC64le once I wiil need this >> support in one of my applications. Would a port of this old piece of code be >> merged on LLVM 3.5, even though it is on the verge of obsoleteness? >> >> Thank you! >> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >
On 10/27/2014 09:17 AM, Hans Wennborg wrote:> 3.5 was already released, and we only merge bug fixes to release branches. > > Caio, do you really need it on 3.5 specifically or are you just asking > if folks are interested to get it into the trunk?FYI, this is related to the old JIT which has been removed from trunk and will not be restored. I'd suggest the OP post a patch to the commits list so that it doesn't get lost, but this is unlikely to make it in to any LLVM release going forward. p.s. Is there a reason the OP is using the old JIT rather than MCJIT?> > - Hans > > On Mon, Oct 27, 2014 at 3:33 AM, Yaron Keren <yaron.keren at gmail.com> wrote: >> +Hans >> >> Caio, even if this patch does not go into 3.5, maybe you'd like to post it >> on llvm-commits so it will be available publicly and not lost. >> >> Yaron >> >> >> 2014-10-27 12:16 GMT+02:00 Caio Souza Oliveira >> <caio.oliveira at eldorado.org.br>: >>> Hello there! >>> >>> I’m intending to port LLVM old JIT API for PPC64le once I wiil need this >>> support in one of my applications. Would a port of this old piece of code be >>> merged on LLVM 3.5, even though it is on the verge of obsoleteness? >>> >>> Thank you! >>> >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Nice, I'm still in planning phases and I'll try some workaround before digging deep to the port. But the information you guys provided me was important to know the acceptance of my port in such a special case. Thank you very much. Caio -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Philip Reames Sent: segunda-feira, 27 de outubro de 2014 14:44 To: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] PPC64 old JIT support On 10/27/2014 09:17 AM, Hans Wennborg wrote:> 3.5 was already released, and we only merge bug fixes to release branches. > > Caio, do you really need it on 3.5 specifically or are you just asking > if folks are interested to get it into the trunk?FYI, this is related to the old JIT which has been removed from trunk and will not be restored. I'd suggest the OP post a patch to the commits list so that it doesn't get lost, but this is unlikely to make it in to any LLVM release going forward. p.s. Is there a reason the OP is using the old JIT rather than MCJIT?> > - Hans > > On Mon, Oct 27, 2014 at 3:33 AM, Yaron Keren <yaron.keren at gmail.com> wrote: >> +Hans >> >> Caio, even if this patch does not go into 3.5, maybe you'd like to >> post it on llvm-commits so it will be available publicly and not lost. >> >> Yaron >> >> >> 2014-10-27 12:16 GMT+02:00 Caio Souza Oliveira >> <caio.oliveira at eldorado.org.br>: >>> Hello there! >>> >>> I’m intending to port LLVM old JIT API for PPC64le once I wiil need >>> this support in one of my applications. Would a port of this old >>> piece of code be merged on LLVM 3.5, even though it is on the verge of obsoleteness? >>> >>> Thank you! >>> >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev_______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev