Hi everyone, This is just a note to mention that the PowerPC JIT is now operational and begging for testing in mainline CVS. There is one known problem (below), but otherwise it works as well as the static PowerPC backend on the test suite. The known problem is that the JIT seems unable to resolve calls to external functions that start with "__", such as __eprintf, __moddi3, etc. This appears to be something funny in the darwin implementation of dlsym (returning null for symbols that are valid if they start with __). If anyone has any ideas of how to make this work, we would love to hear them. :) -Chris -- http://llvm.org/ http://nondot.org/sabre/
Well, one of these days we'll be using libltdl (libtool's dynamic library support) to make the interface to dynamic libraries consistent, somewhat portable, and to get rid of system specific differences like this. Reid. On Sun, 2004-11-28 at 10:00, Chris Lattner wrote:> Hi everyone, > > This is just a note to mention that the PowerPC JIT is now operational and > begging for testing in mainline CVS. There is one known problem (below), > but otherwise it works as well as the static PowerPC backend on the test > suite. > > The known problem is that the JIT seems unable to resolve calls to > external functions that start with "__", such as __eprintf, __moddi3, etc. > This appears to be something funny in the darwin implementation of dlsym > (returning null for symbols that are valid if they start with __). If > anyone has any ideas of how to make this work, we would love to hear them. > :) > > -Chris-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041128/562099a2/attachment.sig>
FYI .. if you want to see how this works, check out lib/System/DynamicLibrary.cpp and platform versions of it. Reid. On Sun, 2004-11-28 at 10:03, Reid Spencer wrote:> Well, one of these days we'll be using libltdl (libtool's dynamic > library support) to make the interface to dynamic libraries consistent, > somewhat portable, and to get rid of system specific differences like > this. > > Reid. > > On Sun, 2004-11-28 at 10:00, Chris Lattner wrote: > > Hi everyone, > > > > This is just a note to mention that the PowerPC JIT is now operational and > > begging for testing in mainline CVS. There is one known problem (below), > > but otherwise it works as well as the static PowerPC backend on the test > > suite. > > > > The known problem is that the JIT seems unable to resolve calls to > > external functions that start with "__", such as __eprintf, __moddi3, etc. > > This appears to be something funny in the darwin implementation of dlsym > > (returning null for symbols that are valid if they start with __). If > > anyone has any ideas of how to make this work, we would love to hear them. > > :) > > > > -Chris > > ______________________________________________________________________ > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041128/8223caaf/attachment.sig>
Le Sun, Nov 28, 2004 at 12:00:03PM -0600, Chris Lattner écrivait/wrote:> > > This is just a note to mention that the PowerPC JIT is now operational and > begging for testing in mainline CVS. There is one known problem (below), > but otherwise it works as well as the static PowerPC backend on the test > suite. [....]I'll be delighted to test it, but so fare I was not able to compile LLVM, even on x86 (without the llvmgcc which I don't use). Are there precise build & use instructions for newbies wanting to test LLVM *in JIT mode only* (I did not found any)? Again, I do not xant to use any llvmgcc stuff... I don't need it (and if it where absolutely needed for JIT use of LLVM I would give up using LLVM for JIT...) Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net 8, rue de la Faïencerie, 92340 Bourg La Reine, France
On Sun, 2004-11-28 at 10:27, Basile STARYNKEVITCH wrote:> Le Sun, Nov 28, 2004 at 12:00:03PM -0600, Chris Lattner écrivait/wrote: > > > > > > This is just a note to mention that the PowerPC JIT is now operational and > > begging for testing in mainline CVS. There is one known problem (below), > > but otherwise it works as well as the static PowerPC backend on the test > > suite. [....] > > I'll be delighted to test it, but so fare I was not able to compile > LLVM, even on x86 (without the llvmgcc which I don't use).You don't need llvmgcc to get the basic LLVM compiled. Just build with "make tools-only".> Are there precise build & use instructions for newbies wanting to test > LLVM *in JIT mode only* (I did not found any)?Not specifically for "JIT mode only" but you should review: http://llvm.cs.uiuc.edu/docs/GettingStarted.html> > Again, I do not xant to use any llvmgcc stuff... I don't need it (and > if it where absolutely needed for JIT use of LLVM I would give up > using LLVM for JIT...)Should be fine, just don't build the runtime stuff.> > Regards.-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041128/5f09bf3f/attachment.sig>
On Sun, 28 Nov 2004, Basile STARYNKEVITCH wrote:> > This is just a note to mention that the PowerPC JIT is now operational and > > begging for testing in mainline CVS. There is one known problem (below), > > but otherwise it works as well as the static PowerPC backend on the test > > suite. [....] > > I'll be delighted to test it, but so fare I was not able to compile > LLVM, even on x86 (without the llvmgcc which I don't use).Sure, just follow the getting started guide, which will show you have to build LLVM.> Are there precise build & use instructions for newbies wanting to test > LLVM *in JIT mode only* (I did not found any)?Without the CFE, there are not a whole lot of ways to get LLVM bytecode to test, but the llvm/examples directory contains several example programs that build LLVM code on the fly and JIT it, that should do the job. -Chris -- http://llvm.org/ http://nondot.org/sabre/