search for: lifelongoptimizationtr

...their address, and they do not live in memory. In fact, LLVM does not have an "address of" operator. Stack memory is all explicitly allocated with the 'alloca' instruction. See Section 2.3 of this paper for more discussion on this topic: http://llvm.cs.uiuc.edu/pubs/2003-09-30-LifelongOptimizationTR.html > > This gives us some very nice properties: for example the C/C++ > > front-end does not have an "SSA construction pass", instead all > > automatic variables live on the stack (in memory) and are accessed via > > loads & stores. As such, no values are l...

...live in memory. In > fact, > LLVM does not have an "address of" operator. Stack memory is all > explicitly allocated with the 'alloca' instruction. See Section 2.3 of > this paper for more discussion on this topic: > > http://llvm.cs.uiuc.edu/pubs/2003-09-30-LifelongOptimizationTR.html > >>> This gives us some very nice properties: for example the C/C++ >>> front-end does not have an "SSA construction pass", instead all >>> automatic variables live on the stack (in memory) and are accessed >>> via >>> loads & sto...

...ent and will eventually lose the ugly purple bars :) 8. Brian spiffed up llvm-nm to support archive files. 9. We just found out that the LLVM overview paper we sent to CGO got accepted! If you're interested, our submission is available here: http://llvm.cs.uiuc.edu/pubs/2003-09-30-LifelongOptimizationTR.html As you can see, we've fixed a LOT of bugs since 1.0. If you can, I highly recommend trying out the leading edge CVS tree for the LLVM core: it has all of the bugfixes in it, and should be stable. If you don't want to do that, we are probably going to release 1.1 in the next couple...

On Thu, 6 Nov 2003, Michelle Strout wrote: > Those of us working on the OpenAnalysis project have been looking at > LLVM recently (excellent job on the website BTW). Thanks! I'm just one of the many people who have worked on it though, the praise belongs to them as much as it does to me. :) > This includes researchers at Rice, Argonne, and LLNL. Great! > John Mellor-Crummey

Chris Lattner wrote: > On Fri, 19 Dec 2003, Yueqiang wrote: > > >>In high level languge there are usually have time and sync instruction, >>to handle async and sync operation. >>I want to know how LLVM take an count of these. > > > I'm not sure exactly what 'time' and 'sync' operations you're talking > about, or what languages