similar to: [LLVMdev] llc -march=ia64 support

Hi there, The IA64 architecture, which had its 'official' name changed to the "Itanium Processor Architecture", *is* supported by llc. I am pretty sure you are talking about the x86-64 architecture, which has also had its share of unfortunate name changes and is also known as "AMD64", "EM64T" and all sorts of things in between. x86-64 is *not* currently

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 all, I am involved in a compiler project for Transport Triggered Architectures (think VLIW and you are pretty close), and we are considering using LLVM. Browsing the list archives, I noticed an announcement of Python bindings for LLVM 1.5. Does anyone know the current status of the bindings? -- Pertti

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

Hello LLVM-ers, The next sprint of PyPy will be held in Dallas, Texas, at the PyCon conference. Most of you know about the LLVM back-end of PyPy. So far, we use mostly the static compilation features of LLVM, but as we are progressing on the JIT side we are considering starting sometime soon working on just-in-time machine code generation backends. Clearly, LLVM might prove to be a good target

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

On Fri, 23 Dec 2005, Eric van Riet Paap wrote: > 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

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

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 ==============================================================

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

On Fri, 31 Oct 2003, Armin Rigo wrote: > Hello Chris, > > We have been investigating your project and the good documentation > and are very impressed. If we understood your goals correctly > this seems like a good match for our ongoing and active PyPy project, > a reimplementation of the Python language in Python. Cool. We are all big fans of Python here. :) > We'll

Hello, I would like to ask the llvm developers to have a look at http:// llvm.org/bugs/show_bug.cgi?id=918 . This bug has been reported 4 month ago but is none the less a somewhat serious one. Below I have pasted the test case and output of the issue running on my ppc machine. thank you Eric pb:~ eric$ cat testme.ll;llvm-as -f testme.ll;llc -march=c -f testme.bc;gcc -c testme.cbe.c

Hi all, For those of you following PyPy, our next sprint has "porting to LLVM 2.0" as one of its topics. ======================================================== Vilnius/Post EuroPython PyPy Sprint 12-14th of July ======================================================== The PyPy team is sprinting at EuroPython again and we invite you to participate in our 3 day long sprint at the

[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

Hi LLVM-dev! As you know, I'm involved with the PyPy Python compiler effort and have been wroking on the LLVM backend. The LLVM backend will be one of the topics of the upcoming PyPy sprint (see link below), which will take place in Heidelberg, Germany. See sprint announcement below or on http://codespeak.net/pypy/index.cgi?extradoc/sprintinfo/Heidelberg-sprint.html Since we only started

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

Eric van Riet Paap wrote: > *testme.cbe.c:106: error: array type has incomplete element type* The problem code boils down to: /* Structure forward decls */ struct l_structtype_s; /* Typedefs */ typedef struct l_structtype_s l_fixarray_array3[3]; which is illegal C, but perfectly valid C++, and g++ accepts it. The structure contents are defined right afterwards, but I assume that

<cc'ing llvmdev> On Tue, 28 Nov 2006, Eric van Riet Paap wrote: > I'm working on using the LLVM JIT in PyPy and I hop you can give me a few > hint. ok > I have some things working at and try to write C++ code for what I need > from Python. The unittest I am working on at the moment is looks like > this > > --- Python code... > llglobalmul4 =

Hi Armin, > The next sprint of PyPy will be held in Dallas, Texas, at the PyCon > conference. Most of you know about the LLVM back-end of PyPy. So > far, > we use mostly the static compilation features of LLVM, How are you using the static compilation features? Are you able to do this via API calls or generating code that will be processed by tools? Thanks, Marcel

Hi all, We're proud to announce... ========================================== PyPy 1.0: JIT compilers for free and more ========================================== Welcome to the PyPy 1.0 release - a milestone integrating the results of four years of research, engineering, management and sprinting efforts, concluding the 28 months phase of EU co-funding! Although still not mature enough