Chris Lattner wrote:>I can't reproduce this failure with mainline CVS using either lli or llc: > >$ lli -regalloc=linearscan a.out.bc >$ echo $status >0 > >Are you sure that the CVS version is in your path? > >After configure and make I run make install, which moves the executables to /usr/local/bin, right ? And yes, they are in my path. But thank you very much for trying to reproduce the problem. It must be some configuration problem on my side then. I do see other strange problems, such as a long list of type conflicts when linking c++ programs. I will clean up everything and install all over. Best regards /Finn
Finn S Andersen wrote:> Chris Lattner wrote: > >> I can't reproduce this failure with mainline CVS using either lli or llc: >> >> $ lli -regalloc=linearscan a.out.bc >> $ echo $status >> 0 >> >> Are you sure that the CVS version is in your path? >> >> > After configure and make I run make install, which moves the executables > to /usr/local/bin, right ? And yes, they are in my path.I am not sure if the "make install" target will work as expected. Generally, we compile LLVM and set our paths to the OBJECT_ROOT/tools/Debug directory (as described in the LLVM "Getting Started" guide). I seem to recall that someone added some support for the install target, but I don't know if it is complete. If any work as been done, it has probably been registered in BugZilla as an enhancement.> > But thank you very much for trying to reproduce the problem. It must be > some configuration problem on my side then. I do see other strange > problems, > such as a long list of type conflicts when linking c++ programs. I will > clean up everything and install all over. > > Best regards > /Finn > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://mail.cs.uiuc.edu/mailman/listinfo/llvmdevRegards, -- John T. -- ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu * * Research Programmer * * University of Illinois at Urbana-Champaign * * * * "It's today!" said Piglet. "My favorite day," said Pooh. * *********************************************************************
Sorry to disturb you all, but I simply cannot get the linearscan allocator to work. I have upgraded llvm to mainline cvs. Everything works until I get to llc -regalloc=linearscan or lli -regalloc=linearscan. I have installed it on redhat 9 and on Fedora Core distributions (I even took it as far as to format a new partition and install Fedora core all over). I have submitted the bytecode that triggers the error, but IT WORKS JUST FINE for John (see below). Apparently, the error only shows itself on my installation. Guess I must be making some stupid mistake with my configuration. I do believe that I follow the recipe given. Now I'm stuck. Any kind of even remote ideas about what kind of strange dependencies I have violated ? Anybody running it on RedHat Linux ? RedHat has been known to ship installations with problems before, like when they shipped it with a strange gcc version. Any kind of help is most welcome. Thanks in advance, /Finn John Criswell wrote:> Finn S Andersen wrote: > >> Chris Lattner wrote: >> >>> I can't reproduce this failure with mainline CVS using either lli or >>> llc: >>> >>> $ lli -regalloc=linearscan a.out.bc >>> $ echo $status >>> 0 >>> >>> Are you sure that the CVS version is in your path? >>> >>> >> After configure and make I run make install, which moves the executables >> to /usr/local/bin, right ? And yes, they are in my path. > > > I am not sure if the "make install" target will work as expected. > Generally, we compile LLVM and set our paths to the > OBJECT_ROOT/tools/Debug directory (as described in the LLVM "Getting > Started" guide). I seem to recall that someone added some support for > the install target, but I don't know if it is complete. If any work > as been done, it has probably been registered in BugZilla as an > enhancement.