search for: vanrietpaap

Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because noone will be there dedicated to LLVM. If however someone would like to participate we will make sure some of the PyPy

Hi, Before experimenting with these settings: how do I know what the defaults are? cheers, Eric

>> <snip>. >> void add_global_mapping(const char* name, void* address) { >> GlobalVariable var(Type::IntTy, false, >> GlobalVariable::ExternalLinkage, 0, name, gp_module); >> gp_execution_engine->addGlobalMapping(&var, address); >> } > > This is creating a new global variable on the stack, instead of > finding the existing

Hi Pertti, The boost Python are not (yet) part of LLVM so I suppose it would make most sense to try to makes fixes/changes so they would work for 1.7 and then try to get them into LLVM CVS. It would be good in such a case to ask the author of the bindings again if he would allow this, because basicaly I think he has to agree to the LLVM lincense. cheers, Eric On Apr 20, 2006, at 5:08

Hi, The person that developed the bindings is Jarno Seppänen , he sent me the code a few weeks ago. They were build with Boost.Python. The latest version was for LLVM 1.6 and the bindings seem to be unmaintained at the moment. From what I could tell they are very clean and probably easy to maintain/update to LLVM 1.7. From what I could tell from the email archive they were not far from

hello everyone, I few days ago I had some code (for the PyPy project) that llc - march=c converted to a switch statement and gcc compiled that nicely to a jumptable in the .s file. Now I try to reproduce when directly going from a .ll to a .s file. But I now see a long list of compare and jumps instead of the jumptable. Is there a transformation that does this if->switch(ing) or is

pypy-0.7.0: first PyPy-generated Python Implementations ============================================================== What was once just an idea between a few people discussing on some nested mailing list thread and in a pub became reality ... the PyPy development team is happy to announce its first public release of a fully translatable self contained Python implementation. The 0.7 release

[The first part of the announcement did not make it into the previous mail] Hello LLVM-ers, Most of you know of the LLVM backend in PyPy. We would like to use LLVM JIT for the next phase of PyPy. If any of you would like to help us, please come to Gothenburg next december. We have not put an LLVM track on the todo-list below mainly because no one will be there dedicated to LLVM. If

I think using different settings is generally (and this this case too) a bad idea because it makes things more complicated. All developers know how to build LLVM. Most (new/casual) users expect a certain behaviour and they will judge LLVM on subjective grounds. If linking/performance suffers they will continue looking for whatever gives them that extra bit of performance. People like me

Hello LLVM-ers, Below you will a description of our new PyPy release, a project which (among many other things)generates one of the largest .ll files in existance. :-) This .ll gets compiled with the LLVM toolchain into a standalone executable of the Python language. I hope you find this interesting! cheers, Eric van Riet Paap ==============================================================

On Nov 13, 2006, at 9:01 AM, Reid Spencer wrote: > On Mon, 2006-11-13 at 01:10 -0800, Chris Lattner wrote: >> On Mon, 13 Nov 2006, Eric van Riet Paap wrote: >>> I must say I also was in need of this document but never knew it >>> existed. It seems to be linked from the faq page only. I only read >>> that the first day I came to LLVM. Maybe linking it from the

Hi, I must say I also was in need of this document but never knew it existed. It seems to be linked from the faq page only. I only read that the first day I came to LLVM. Maybe linking it from the GetElementPtr instruction in LangRef.html would make sense. cheers Eric On Nov 12, 2006, at 8:47 PM, Reid Spencer wrote: > Ram, > > Please read and understand the GetElementPtr FAQ

Hi, For the PyPy project ( http://codespeak.net/pypy ) I am working on the x64-64 support. I would like to use llc -march=ia64 to generate the assembly but that is not supported at the moment. As a workaround I let llc generate C code that gets compiled, but this unfortunately is not a good way to show the power of llvm. A understood this ia64 support will be worked on soon. First week of july

You are right, the machine I am on is a AMD Opteron. I could probably generate working code for x86, but I am testing the implications of using 64 bits integers. The four weeks is not really important, it's just that it would be nice to have really fast code to showcase. Something related to this: to test the effect of 64 bits integers I replace all reference of int by long in my .ll file.

Hello LLVM, During this sprint we will also look at using LLVM JIT for our project. What exactly we will do in Tokyo very much depends on who will attend. So if you are interested please contact me beforehand so we can make sure everyone will have a fun and productive time. cheers, Eric van Riet Paap Tokyo PyPy Sprint: 23rd - 29th April 2006