From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75276] Implement VGPR Register Spilling
Date: Sat, 17 May 2014 08:37:07 +0000 [thread overview]
Message-ID: <bug-75276-502-jARFy5ZqAH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75276-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2963 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75276
--- Comment #14 from farmboy0+freedesktop@googlemail.com ---
The v3 patch doesnt fix Antichamber's crash to desktop.
But with this patch it actually shows the VGPR messages:
LLVM triggered Diagnostic Handler: SIInstrInfo::storeRegToStackSlot - Can't
spill VGPR!
LLVM triggered Diagnostic Handler: SIInstrInfo::loadRegToStackSlot - Can't
retrieve spilled VGPR!
Here's the start of the backtrace for reference:
Program received signal SIGSEGV, Segmentation fault.
0xf504f671 in std::pair<llvm::SlotIndex, llvm::SlotIndex>::operator=
(this=0x450d2ff4, __p=...)
at
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4/bits/stl_pair.h:153
153 second = __p.second;
(gdb) bt
#0 0xf504f671 in std::pair<llvm::SlotIndex, llvm::SlotIndex>::operator=
(this=0x450d2ff4, __p=...)
at
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4/bits/stl_pair.h:153
#1 0xf505e8c5 in llvm::IntervalMapImpl::NodeBase<std::pair<llvm::SlotIndex,
llvm::SlotIndex>, llvm::LiveInterval*, 16u>::copy<16u> (
this=0x44ee9644, Other=..., i=250679, j=250678, Count=4294967295)
at /mnt/daten/Daten/Repositories/llvm/include/llvm/ADT/IntervalMap.h:231
#2 0xf505f3ad in llvm::IntervalMapImpl::NodeBase<std::pair<llvm::SlotIndex,
llvm::SlotIndex>, llvm::LiveInterval*, 16u>::moveLeft (
this=0x44ee9644, i=1, j=0, Count=4294967295) at
/mnt/daten/Daten/Repositories/llvm/include/llvm/ADT/IntervalMap.h:242
#3 0xf505ec81 in llvm::IntervalMapImpl::NodeBase<std::pair<llvm::SlotIndex,
llvm::SlotIndex>, llvm::LiveInterval*, 16u>::erase (
this=0x44ee9644, i=0, j=1, Size=0) at
/mnt/daten/Daten/Repositories/llvm/include/llvm/ADT/IntervalMap.h:263
#4 0xf505e175 in llvm::IntervalMapImpl::NodeBase<std::pair<llvm::SlotIndex,
llvm::SlotIndex>, llvm::LiveInterval*, 16u>::erase (
this=0x44ee9644, i=0, Size=0) at
/mnt/daten/Daten/Repositories/llvm/include/llvm/ADT/IntervalMap.h:270
#5 0xf505d1ee in llvm::IntervalMap<llvm::SlotIndex, llvm::LiveInterval*, 16u,
llvm::IntervalMapInfo<llvm::SlotIndex> >::iterator::erase (
this=0xffff6348) at
/mnt/daten/Daten/Repositories/llvm/include/llvm/ADT/IntervalMap.h:1876
#6 0xf505c846 in llvm::LiveIntervalUnion::extract (this=0x44ee9640,
VirtReg=...) at LiveIntervalUnion.cpp:68
#7 0xf50655ef in llvm::LiveRegMatrix::unassign (this=0x44d26e60, VirtReg=...)
at LiveRegMatrix.cpp:96
#8 0xf511e81f in (anonymous namespace)::RAGreedy::tryLastChanceRecoloring
(this=0x44243000, VirtReg=..., Order=..., NewVRegs=...,
FixedRegisters=..., Depth=0) at RegAllocGreedy.cpp:2067
#9 0xf511f224 in (anonymous namespace)::RAGreedy::selectOrSplitImpl
(this=0x44243000, VirtReg=..., NewVRegs=..., FixedRegisters=...,
Depth=0) at RegAllocGreedy.cpp:2285
#10 0xf511eb60 in (anonymous namespace)::RAGreedy::selectOrSplit
(this=0x44243000, VirtReg=..., NewVRegs=...) at RegAllocGreedy.cpp:2144
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3793 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-17 8:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 18:56 [Bug 75276] New: Implement VGPR Register Spilling bugzilla-daemon
2014-02-20 18:57 ` [Bug 75276] " bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-20 18:58 ` bugzilla-daemon
2014-02-24 17:45 ` bugzilla-daemon
2014-03-04 6:47 ` bugzilla-daemon
2014-03-04 6:51 ` bugzilla-daemon
2014-04-17 13:11 ` bugzilla-daemon
2014-04-28 18:46 ` bugzilla-daemon
2014-04-28 20:51 ` bugzilla-daemon
2014-04-29 21:36 ` bugzilla-daemon
2014-05-13 15:00 ` bugzilla-daemon
2014-05-16 19:27 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:02 ` bugzilla-daemon
2014-05-17 3:03 ` bugzilla-daemon
2014-05-17 3:11 ` bugzilla-daemon
2014-05-17 8:37 ` bugzilla-daemon [this message]
2014-05-17 12:40 ` bugzilla-daemon
2014-05-17 14:54 ` bugzilla-daemon
2014-05-17 17:40 ` bugzilla-daemon
2014-05-17 17:41 ` bugzilla-daemon
2014-05-17 18:44 ` bugzilla-daemon
2014-05-18 0:32 ` bugzilla-daemon
2014-05-18 0:37 ` bugzilla-daemon
2014-05-18 10:41 ` bugzilla-daemon
2014-05-19 13:50 ` bugzilla-daemon
2014-05-19 13:50 ` bugzilla-daemon
2014-05-19 22:51 ` bugzilla-daemon
2014-06-16 17:08 ` bugzilla-daemon
2014-06-28 9:58 ` bugzilla-daemon
2014-07-03 21:20 ` bugzilla-daemon
2014-07-13 4:33 ` bugzilla-daemon
2014-07-24 11:58 ` bugzilla-daemon
2014-07-28 10:08 ` bugzilla-daemon
2014-07-28 11:10 ` bugzilla-daemon
2014-07-29 3:31 ` bugzilla-daemon
2014-07-29 3:33 ` bugzilla-daemon
2014-08-28 12:15 ` bugzilla-daemon
2014-08-28 12:19 ` bugzilla-daemon
2014-08-28 12:21 ` bugzilla-daemon
2014-08-29 7:19 ` bugzilla-daemon
2014-09-07 13:28 ` bugzilla-daemon
2014-09-07 16:10 ` bugzilla-daemon
2014-09-07 16:12 ` bugzilla-daemon
2014-09-07 20:21 ` bugzilla-daemon
2014-09-13 17:39 ` bugzilla-daemon
2014-09-17 6:55 ` bugzilla-daemon
2014-09-19 1:11 ` bugzilla-daemon
2014-09-19 23:58 ` bugzilla-daemon
2014-09-20 9:01 ` bugzilla-daemon
2014-09-24 17:11 ` bugzilla-daemon
2014-09-25 20:38 ` bugzilla-daemon
2014-09-26 17:16 ` bugzilla-daemon
2014-11-08 9:55 ` bugzilla-daemon
2014-11-10 14:34 ` bugzilla-daemon
2014-11-11 1:38 ` bugzilla-daemon
2014-11-21 10:24 ` bugzilla-daemon
2015-01-07 22:10 ` bugzilla-daemon
2015-01-08 7:48 ` bugzilla-daemon
2015-01-09 20:18 ` bugzilla-daemon
2015-01-13 19:12 ` bugzilla-daemon
2015-01-13 19:15 ` bugzilla-daemon
2015-01-13 19:18 ` bugzilla-daemon
2015-02-05 15:52 ` bugzilla-daemon
2015-02-05 15:56 ` bugzilla-daemon
2015-02-06 1:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-75276-502-jARFy5ZqAH@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).