[Bug 73320] New: [radeonsi] LLVM runs out of registers during register allocation in Painkiller Hell & Damnation

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 6 04:42:13 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=73320

          Priority: medium
            Bug ID: 73320
          Assignee: dri-devel at lists.freedesktop.org
           Summary: [radeonsi] LLVM runs out of registers during register
                    allocation in Painkiller Hell & Damnation
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: freedesktop.org at inequation.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

(this is possibly a duplicate of bug #72228)

First of all, this report is based on a user's report - I do not have the
software/hardware combo to reproduce. I can, however, provide Steam keys for
the game to Mesa developers for free if it is needed, just shoot me an email.

A user of Painkiller Hell & Damnation has reported crashes when using radeonsi
from Mesa 10.1.0-devel (git-5a51c1b saucy-oibaf-ppa). LLVM aborts with the
following message:

LLVM ERROR: ran out of registers during register allocation

Relevant part of the backtrace:

#7  0xb7a20791 in __run_exit_handlers (status=status at entry=1, listp=0xb7b9d3e4
<__exit_funcs>, run_list_atexit=run_list_atexit at entry=true)
    at exit.c:77
#8  0xb7a2081d in __GI_exit (status=1) at exit.c:99
#9  0xb5d28ee3 in llvm::report_fatal_error(llvm::Twine const&, bool) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#10 0xb5d28fdb in llvm::report_fatal_error(char const*, bool) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#11 0xb54cf6de in llvm::RegAllocBase::allocatePhysRegs() () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#12 0xb54dec28 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#13 0xb545781e in llvm::MachineFunctionPass::runOnFunction(llvm::Function&) ()
from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#14 0xb5638974 in llvm::FPPassManager::runOnFunction(llvm::Function&) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#15 0xb5638a28 in llvm::FPPassManager::runOnModule(llvm::Module&) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#16 0xb563b195 in llvm::legacy::PassManagerImpl::run(llvm::Module&) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#17 0xb563b336 in llvm::legacy::PassManager::run(llvm::Module&) () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#18 0xb5da1bb9 in ?? () from /usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#19 0xb5da1f30 in LLVMTargetMachineEmitToMemoryBuffer () from
/usr/lib/i386-linux-gnu/libLLVM-3.4.so.1
#20 0xb6b92b17 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#21 0xb6b80f30 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#22 0xb6b81a9e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#23 0xb6b8a382 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#24 0xb6b8a4e3 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#25 0xb698f60e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#26 0xb6990966 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#27 0xb6956443 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#28 0xb695339e in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#29 0xb6968230 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#30 0xb6937891 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#31 0xb6938e4c in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#32 0xb6939254 in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#33 0xb693934f in ?? () from /usr/lib/i386-linux-gnu/dri/radeonsi_dri.so
#34 0x08b65086 in FMeshDrawingPolicy::DrawMesh(FMeshBatch const&, int) const ()

Anything I can do to improve the diagnostics?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140106/22c74df4/attachment-0001.html>


More information about the dri-devel mailing list