similar to: [LLVMdev] LLVM Status Update

Ok, the last status update (http://mail.cs.uiuc.edu/pipermail/llvmdev/2003-June/000416.html) was over 7 weeks ago, sorry about that. We've been really busy squishing bugs, improving stability, and otherwise improving the system for the release. Here are some of the major accomplishments in LLVM since the last update... 1. We finally have the go-ahead from the university to release LLVM

Hi all LLVMers! It's time for another dose of LLVM status update. Since 1.1, we've fixed 34 new LLVM bugs (including a lot of quality-of-implementation bugs), sped up the optimizer, and even implemented some new features. Here are the highlights: 1. Misha reorganized the sparc backend to be a bit more modular and cleaned up the asmwriter. 2. The JIT now lazily initializes global

Hey everyone, It's been way too long since the last status update. Since that last edition, we've gone through the 1.0 release, fixed a ton of bugs, and implemented some neat new things. Since many people are using the 1.0 release, I'll break the changes into "before 1.0" and "after 1.0" sections: Before 1.0: ----------- 1. We've cleaned up the source base

Hi everyone, This Fall has been busy, busy, busy. In addition to the usual LLVM hacking, our developers have been moving all over the country, starting classes, ending internships, getting married, and traveling the world. Despite all of the non-LLVM fun we've been having, we've managed to get some work done, too. :) Here is my traditional distillation of llvm-commits: New High-Level

Hi everyone, Here's an update on what we've been up to and how the LLVM 1.0 release is shaping up. Overall, things are going well, and it looks highly likely that we'll get the release out by the end of the month! Here's the hilights of the last few weeks: 1. John checked in support for building LLVM into multiple different object directories in the Autoconf style. He also

The LLVM 1.4 Release is now out! Get it here: http://llvm.cs.uiuc.edu/releases/ or read about it here: http://llvm.cs.uiuc.edu/releases/1.4/docs/ReleaseNotes.html#whatsnew This release features a huge assortment of improvements in functionality, generated code quality, and compile times. Thanks to everyone who has helped make this release the best one yet. In addition to the changes

Hi Everyone, Sorry for the long overdue status update, as you might guess, the holidays have been busy for everyone. :) Here's your periodic dose of updates on the progress of LLVM, which takes us from the LLVM 1.4 release until present CVS. I appologize if I forgot anything! Big Things: 1. Brian contributed a new SparcV8 backend, which (unlike the SparcV9 backend) uses the

On Thu, 17 Jun 2004, Tobias Nurmiranta wrote: > > Thanks for the fast reply. I'll do as you suggested, and create my own > identity instructions with "add" for int's and "getelementptr" for > pointers. Another thing to point out is that this might only be happening because your front-end is attempting to generate SSA. In general, we don't recommend

LLVM list, I bumped into Alex Friedman in the hall today and by coincidence he mentioned that they were switching to LLVM for their PLT Scheme JIT project. I had evaluated LLVM a few weeks ago for my own purposes, but decided that it was too C/C++ centered and that critical features such as tail call optimization and other stack manipulation features were likely stagnant. So naturally I asked

On Thu, Jun 17, 2004 at 05:09:30PM +0200, Tobias Nurmiranta wrote: > A small thing I miss in the intermediate representation is a simple > assignment instruction, like: > > %x = uint 3 > or: > %x = uint %y > > It would simplify the implementation of frontends, I think. Neither of these is necessary, and adding new instructions means every transformation has to handle

On Thu, 5 May 2005, Misha Brukman wrote: > On Thu, May 05, 2005 at 03:46:58AM -0400, Alexander Friedman wrote: >> On May 5, Misha Brukman wrote: >>> To the best of my knowledge, this has not been done and no one has >>> announced their intent to work on it, so if you are interested, >>> you'd be more than welcome to do so. >> >> My C++ knowledge

On Mon, May 16, 2005 at 05:15:30PM -0700, John Cortes wrote: > If I use any of the regalloc parameters (local, ...) I get an error in > the LiveVariable.cpp file, in the part that I think cheaks for dead > code because a Variable didn't have a defined Instance to a Machine > instruction. > > " llc: LiveVariables.cpp:86: void >

On Sat, Apr 15, 2006 at 07:47:00AM +0200, Oscar Fuentes wrote: > Simon Burton <simon at arrowtheory.com> writes: > > I've read over the "LLVM Language Reference Manual" > > a few times, and writing some ll code, but i'm stuck at > > a very basic point. How to decrement a counter variable ? [snip] > > I guess I could malloc a variable and use

Thanks for the fast reply. I'll do as you suggested, and create my own identity instructions with "add" for int's and "getelementptr" for pointers. , Tobias On Thu, 17 Jun 2004, Misha Brukman wrote: > On Thu, Jun 17, 2004 at 05:09:30PM +0200, Tobias Nurmiranta wrote: > > A small thing I miss in the intermediate representation is a simple > > assignment

On Thu, Jul 08, 2004 at 11:12:58AM -0500, Vikram Adve wrote: > PHI nodes within machine code were originally used by the Sparc > back-end but they turned out not to be necessary. Actually, they are currently used in non-SparcV9 backends (see below). > Instead, LLVM phis are lowered to copy instructions in the machine > code (I believe this happens just after instruction selection).

Sorry for the confusion, Misha seemed to answer my question in one way. It'll be easier if I break down my question into parts - - Is it possible to see the SSA form generated for my program ? - Now, if this form is readable, is it in assembly code format ? We want to look at the SSA form for any program and see if we can make some changes ourselves to that format so that its reflected in

On Fri, 9 Jul 2004, Vladimir Prus wrote: > Misha Brukman wrote: > > > LLVM Machine code is in SSA. > > This explains quite a lot. I though it's possible to just reduce convert phis > into copy instructions in predecessors -- all of which will have the same > destination register. There are algorithms for eliminating PHI nodes, but they aren't quite so simple.

2009/3/27 Andre Tavares <andrelct at dcc.ufmg.br> > I'm a Computer Science master student at UFMG, Brasil. I'm interested in > taking part on Google Summer of Codes 2009. My idea is not on the LLVM list, > but I have written a project description to make my intentions clear. My > project is attached as a pdf file. By changing LLVM IR from SSA to SSI, you propose to

On Wed, May 05, 2004 at 03:35:46PM +0200, Anders Alexandersson wrote: > %tmpFunction = load int ()** %puts_kernelPTR > ... > %tmpFunction = load int ()** %puts_kernelPTR > > generates > > Redefinition of value named 'tmpFunction' in the 'int () *' type plane! > > Is it not allowed to reuse variables? Is there some way to do it? LLVM uses the Static

On Thu, Jul 08, 2004 at 08:06:29PM +0400, Vladimir Prus wrote: > Could anybody quickly explain why PHI nodes instructions are necessary > in machine code? And why the code in LiveVariables.cpp which looks at > those PHI nodes (line 249 and below) is necessary. LLVM Machine code is in SSA. Let's say you want to do r = a cond b But doing this: if (a cond b) then r = 1