From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69805] flightgear crashes on r600 (rs880)
Date: Wed, 25 Sep 2013 14:00:33 +0000 [thread overview]
Message-ID: <bug-69805-502-xIiTuGn3X0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69805-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 660 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69805
--- Comment #5 from Vadim Girlin <ptpzz@yandex.ru> ---
The assert in SB seems to be caused by incorrect alu clause size in the
bytecode.
LLVM with enabled asserts also fails to compile that shader for me with the
following message:
llc: R600ControlFlowFinalizer.cpp:259: ClauseFile <anonymous
namespace>::R600Con
trolFlowFinalizer::MakeALUClause(llvm::MachineBasicBlock &,
MachineBasicBlock::i
terator &) const: Assertion `ClauseContent.size() < 128 && "ALU clause is too
bi
g"' failed.
So this looks like a bug in LLVM backend.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1434 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:[~2013-09-25 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 10:52 [Bug 69805] New: flightgear crashes on r600 (rs880) bugzilla-daemon
2013-09-25 11:08 ` [Bug 69805] " bugzilla-daemon
2013-09-25 12:08 ` bugzilla-daemon
2013-09-25 13:07 ` bugzilla-daemon
2013-09-25 13:08 ` bugzilla-daemon
2013-09-25 14:00 ` bugzilla-daemon [this message]
2013-09-25 14:23 ` bugzilla-daemon
2013-09-25 15:14 ` [Bug 69805] flightgear crashes on r600 (rs880) with llvm backend bugzilla-daemon
2013-09-26 15:12 ` bugzilla-daemon
2013-09-27 13:34 ` 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-69805-502-xIiTuGn3X0@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