From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86089] [r600g][mesa 10.4.0-dev] shader failure - r600_sb::bc_finalizer::cf_peephole() when starting Second Life
Date: Tue, 18 Nov 2014 00:43:39 +0000 [thread overview]
Message-ID: <bug-86089-502-KRnZZMo3S0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86089-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=86089
--- Comment #5 from Emil Velikov <emil.l.velikov@gmail.com> ---
>From bug 86418:
I tried launching the Second Life viewer (Kokua 3.7.8 x64) using the latest GIT
version of MESA, and noticed the viewer crashes as soon as it's time to render
the world. The crash only happens when Basic Shaders are enabled.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1477 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-11-18 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 5:05 [Bug 86089] [r600g] shader failure - r600_sb::bc_finalizer::cf_peephole() when starting Second Life bugzilla-daemon
2014-11-10 5:06 ` bugzilla-daemon
2014-11-10 21:51 ` bugzilla-daemon
2014-11-12 4:10 ` bugzilla-daemon
2014-11-12 4:11 ` [Bug 86089] [r600g][mesa 10.4.0-dev] " bugzilla-daemon
2014-11-18 0:42 ` bugzilla-daemon
2014-11-18 0:43 ` bugzilla-daemon [this message]
2014-11-22 0:54 ` bugzilla-daemon
2014-11-28 3:37 ` bugzilla-daemon
2014-11-30 3:31 ` bugzilla-daemon
2015-01-27 10:19 ` bugzilla-daemon
2015-02-02 21:58 ` bugzilla-daemon
2015-02-02 22:03 ` 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-86089-502-KRnZZMo3S0@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