From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82544] New: Unreal Engine 4 Elemental fails to start up on Cape Verde with LLVM assertion failure
Date: Wed, 13 Aug 2014 06:09:38 +0000 [thread overview]
Message-ID: <bug-82544-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1042 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82544
Priority: medium
Bug ID: 82544
Assignee: dri-devel@lists.freedesktop.org
Summary: Unreal Engine 4 Elemental fails to start up on Cape
Verde with LLVM assertion failure
Severity: normal
Classification: Unclassified
OS: All
Reporter: michel@daenzer.net
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 104542
--> https://bugs.freedesktop.org/attachment.cgi?id=104542&action=edit
R600_DEBUG=vs output for failing shader
Trying to start the Elemental demo ends with this LLVM assertion failure:
Elemental: /home/daenzer/src/llvm-git/llvm/lib/CodeGen/VirtRegMap.cpp:369: void
(anonymous namespace)::VirtRegRewriter::rewrite(): Assertion `PhysReg &&
"Invalid SubReg for physical register"' failed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2552 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 reply other threads:[~2014-08-13 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 6:09 bugzilla-daemon [this message]
2014-10-02 7:12 ` [Bug 82544] Unreal Engine 4 Elemental fails to start up on Cape Verde with LLVM assertion failure 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-82544-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.