search for: evlogimenos

On 08/09/05, Alkis Evlogimenos <evlogimenos at gmail.com> wrote: > to those coalesced registers, it is logical that noone will ever query > the liveness of those registers (unless there is a bug somewhere in the Indeed the coalesced registers may logically not be queried since they do not appear in any operand list...

On 08/09/05, Alkis Evlogimenos <evlogimenos at gmail.com> wrote: > representative register (found using a union find algorithm). Note that > the representative register could be a real register if we ever joined > an interval of a real register with one of a virtual register (and this > real register will be th...

Alkis Evlogimenos wrote: > On Wed, 2004-06-09 at 04:56, Vladimir Prus wrote: > > Hello! > > Is there an (semi)automatic way to save registers used by a function? For > > example, on my target I have to store ar0-ar4 and gr0-gr4, gr5, gr6. For > > now I just emit huge prologue code to push...

On Sat, 2005-08-27 at 11:47 -0700, Reid Spencer wrote: > Alkis Evlogimenos wrote: > > It seems that these two classes are the same... Maybe they should be > > merged into 1 class? > > > I think you're looking at something old. MutexLocker doesn't exist any more. llvm/Support/ThreadSupport.h is not generated anymore? -- Alkis

On Thu, May 06, 2004 at 04:06:27PM +0200, Finn S Andersen wrote: > Chris Lattner wrote: > > >I think that we should switch to C constants in this case. Can you try > >#include <math.h> and use HUGE_VAL instead? > > > It works: > > [finna at coplin11 ~/test]$ cat tst.cpp > #include <limits> > #include <iostream> > #include

Alkis Evlogimenos wrote: >As for CVS, I am not sure this should be fixed because there is >really no LLVM bug here :-) > > > No, you are right. But perhaps it is worth it to mention the problem somewhere in the documentation, because there appear to be many installations with this problem (I'v...

On Wed, 2004-06-09 at 05:26, Vladimir Prus wrote: > Alkis Evlogimenos wrote: > > On Wed, 2004-06-09 at 04:56, Vladimir Prus wrote: > > > Hello! > > > Is there an (semi)automatic way to save registers used by a function? For > > > example, on my target I have to store ar0-ar4 and gr0-gr4, gr5, gr6. For > > > now I just emit hu...

On Thu, 2004-07-08 at 07:07, Vladimir Prus wrote: > Vladimir Prus wrote: > > Vladimir Prus wrote: > > > The above-mentioned test contains this: > > > > > > long B53 = - (1LL << 53); > > > > > > strictly speaking, this is not correct code. The C standard says about > > > shift: "if the value of the first operator is ... or

Alkis Evlogimenos wrote: > > But the test still has a problem ;-) > > > > printf("%ld\n", Arg / (1LL << 4)); > > > > Again, the passed value is long long, and format specifier is '%ld'. What > > about the attached patch? > > I think testL has anoth...

It seems that these two classes are the same... Maybe they should be merged into 1 class? -- Alkis

Alkis Evlogimenos wrote: > It seems that these two classes are the same... Maybe they should be > merged into 1 class? > I think you're looking at something old. MutexLocker doesn't exist any more. Reid.

On Wed, 2005-09-07 at 18:24 +0800, Tzu-Chien Chiu wrote: > I though LiveVariables may be invalidated by LiveIntervals, but it's > declared not: > > void LiveIntervals::getAnalysisUsage(AnalysisUsage &AU) const > { > AU.addPreserved<LiveVariables>(); > AU.addRequired<LiveVariables>(); > ... > > LiveInterval may coalesce virtual registers and

On Wed, 2005-09-07 at 15:09 +0800, Tzu-Chien Chiu wrote: > I don't understand the following code snippet in LiveIntervalAnalysis.cpp. > > Why changing the type of the opreand from a virtual register to a > machine register? The register number (reg) is still a virtual > register index (>1024). > > > bool LiveIntervals::runOnMachineFunction(MachineFunction &fn)

Alkis Evlogimenos wrote: [snip] > >>Is anything with "Boost" in name will be rejected right away? > > > Absolutely not! We were using one of the boost libraries before and we > replaced it because it was easy to do and it removed one external dependency > for us, not because it...

Vladimir Prus wrote: > Vladimir Prus wrote: > > The above-mentioned test contains this: > > > > long B53 = - (1LL << 53); > > > > strictly speaking, this is not correct code. The C standard says about > > shift: "if the value of the first operator is ... or greater than ... the > > width of the promoted left operand, the behaviour is

Chris Lattner wrote: >I think that we should switch to C constants in this case. Can you try >#include <math.h> and use HUGE_VAL instead? > It works: [finna at coplin11 ~/test]$ cat tst.cpp #include <limits> #include <iostream> #include <math.h> int main() { std::cerr << std::numeric_limits<float>::infinity() << "\n"; std::cerr

...ing, please edit your Subject line so it > is more specific > than "Re: Contents of LLVMdev digest..." > > > Today's Topics: > > 1. Re: Re: Re: New GCC4-based C/C++/ObjC > front-end for LLVM > (Chris Lattner) > 2. Re: llvm-java state (Alkis Evlogimenos) > 3. Re: Re: Re: New GCC4-based C/C++/ObjC > front-end for LLVM > (Chris Lattner) > 4. printing constants (anubham suresh) > 5. install dirs (Rogelio Serrano) > 6. Re: install dirs (John Criswell) > 7. Re: install dirs (Rogelio Serrano) > 8. Re: prin...

On 29 Apr 2006 20:38:58 -0600, Tom Tromey <tromey at redhat.com> wrote: > >>>>> "Archie" == Archie Cobbs <archie at dellroad.org> writes: > > >> In the JIT, devirtualization looks doable, though somewhat fiddly. At > >> least, that is true for straightforward things like calls to methods > >> in final classes, or calls to

On 4/25/06, Archie Cobbs <archie at dellroad.org> wrote: > Alkis Evlogimenos wrote: > > On 4/25/06, Archie Cobbs <archie at dellroad.org> wrote: > >> Motivation: Java's "first active use" requirement for class initialization. > >> When invoking a static method, it's possible that a class may need to > >> be initialize...

I though LiveVariables may be invalidated by LiveIntervals, but it's declared not: void LiveIntervals::getAnalysisUsage(AnalysisUsage &AU) const { AU.addPreserved<LiveVariables>(); AU.addRequired<LiveVariables>(); ... LiveInterval may coalesce virtual registers and remove identity moves instructions: bool LiveIntervals::runOnMachineFunction(MachineFunction &fn) {