Displaying 7 results from an estimated 7 matches for "assignregorstackslotatinterv".
Did you mean:
assignregorstackslotatinterval
2011 Mar 31
2
[LLVMdev] Unallocated address error triggered from ::RALinScan::assignRegOrStackSlotAtInterval on i386
...igned int>, std::less<unsigned int>, std::allocator<unsigned int> >::erase (this=0xa6bd3f8, __first=..., __last=...)
at /usr/local/gcc/4.5.2/lib/gcc/i686-pc-linux-gnu/4.5.2/../../../../include/c++/4.5.2/bits/stl_tree.h:1449
#14 0x00b52b58 in (anonymous namespace)::RALinScan::assignRegOrStackSlotAtInterval(llvm::LiveInterval*) ()
from /usr/local/llvm/svn-r128446/lib/libLLVM-3.0svn.so
#15 0x0169dc00 in llvm::X86::GR32RegClass () from /usr/local/llvm/svn-r128446/lib/libLLVM-3.0svn.so
Problem occurs when I am attempting to run a large module in JIT, from
ExecutionEngine::runFunction, after sta...
2011 Apr 01
0
[LLVMdev] Unallocated address error triggered from ::RALinScan::assignRegOrStackSlotAtInterval on i386
Hi Yuri,
> I am debugging the memory issue that manifests itself like this:
>
> *** glibc detected *** ../app/app.OWS: free(): invalid pointer: 0x0ad391fc ***
try running under valgrind. Note that if the program being JIT'd corrupts
memory then this can cause the JIT itself to blow up.
Ciao, Duncan.
2005 Sep 17
0
[LLVMdev] Re: Problems Cross Compiling for x86 and ia64
..../llvm-darcslocal/llvm/include/llvm/Analysis/LoopInfo.h
has 336 lines.
(gdb) bt
#0 0x00513d50 in llvm::MachineInstr::getParent (this=0x0) at
/Users/mike/Documents/hpcl/LLVM/obj-llvm-darcslocal/../llvm-darcslocal/llvm/include/llvm/Analysis/LoopInfo.h:433
#1 0x001ca99c in (anonymous
namespace)::RA::assignRegOrStackSlotAtInterval (this=0x8b010f0,
cur=0x8b34114) at
/Users/mike/Documents/hpcl/LLVM/obj-llvm-darcslocal/../llvm-darcslocal/llvm/lib/CodeGen/RegAllocLinearScan.cpp:567
#2 0x001cca64 in (anonymous namespace)::RA::linearScan
(this=0x8b010f0) at
/Users/mike/Documents/hpcl/LLVM/obj-llvm-darcslocal/../llvm-darcslocal/...
2005 Sep 16
2
[LLVMdev] Problems Cross Compiling for x86 and ia64
Hi, I'm having some problems cross-compiling from ppc (OS X) to x86
object files and to ia64, at all. I'd appreciate some advice as to
whether or not I'm actually supposed to be able to do this, and what's
wrong if so.
Here's how I configured it:
../llvm-darcslocal/llvm/configure --with-llvmgccdir=$LLVMGCCDIR
--prefix=$HOME/Documents/hpcl/LLVM/install
The results work fine
2004 Apr 26
2
[LLVMdev] x86 cogen quality
...&& "this is not a register!"' failed.
lli[0x849e768]
lli[0x849e974]
/lib/tls/libc.so.6[0x420277b8]
/lib/tls/libc.so.6(abort+0x1d5)[0x42028c55]
/lib/tls/libc.so.6[0x42021043]
lli(llvm::MRegisterInfo::isPhysicalRegister(unsigned)+0x25)[0x8314863]
lli((anonymous
namespace)::RA::assignRegOrStackSlotAtInterval(llvm::LiveIntervals::Interval*)+0x844)[0x8307d16]
lli((anonymous namespace)::RA::linearScan()+0x3c1)[0x8306aff]
lli((anonymous
namespace)::RA::runOnMachineFunction(llvm::MachineFunction&)+0x1d7)[0x83066f1]
lli(llvm::MachineFunctionPass::runOnFunction(llvm::Function&)+0x28)[0x83144fe]
lli...
2004 Apr 21
0
[LLVMdev] x86 cogen quality
On Wed, Apr 21, 2004 at 11:01:48AM +0200, Finn S Andersen wrote:
> For some of the benchmarks the linear scan regalloc
> works. When it does, results are in the x1.0 - 1.5
> range. Unfortunately, the linear scan allocator breaks
> on most of my code.
Is there a chance you can try cvs? I would be interested to
get a simplified test case where the allocator breaks. A lot of
2004 Apr 21
4
[LLVMdev] x86 cogen quality
Hi, I have a question about x86 code quality.
I have run a few benchmarks and compared the
running time of executables created by LLVM to
executables created by gcc.
It appears that code generated by LLVM is x1.5 - x3
times slower than code generated by gcc, for the x86
For some of the benchmarks the linear scan regalloc
works. When it does, results are in the x1.0 - 1.5
range. Unfortunately,