From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99748] [radeonsi] Civ6 Assert in LLVM SIMachineScheduler.cpp with R600_DEBUG=sisched
Date: Fri, 10 Feb 2017 01:29:07 +0000 [thread overview]
Message-ID: <bug-99748-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1226 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99748
Bug ID: 99748
Summary: [radeonsi] Civ6 Assert in LLVM SIMachineScheduler.cpp
with R600_DEBUG=sisched
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: mike@fireburn.co.uk
QA Contact: dri-devel@lists.freedesktop.org
When running Civ6 using LLVM from git (SHA1's tested
1648ceaabcea762590049a74ce8b934e3bfd4fb2 and
897444660daf9e94c020efc97b63aed7e61db7ac) with R600_DEBUG=sisched and the
latest Mesa it would assert with the following error:
Civ6:
/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999/lib/Target/AMDGPU/SIMachineScheduler.cpp:1584:
void llvm::SIScheduleBlockScheduler::blockScheduled(llvm::SIScheduleBlock*):
Assertion `LiveRegsConsumers[RegP.first] == 0' failed.
This doesn't happen with LLVM-4.0.0-rc1 even when using R600_DEBUG=sisched
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-02-10 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 1:29 bugzilla-daemon [this message]
2017-02-10 20:44 ` [Bug 99748] [radeonsi] Civ6 Assert in LLVM SIMachineScheduler.cpp with R600_DEBUG=sisched bugzilla-daemon
2017-02-12 14:46 ` bugzilla-daemon
2017-02-19 10:11 ` 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-99748-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.