From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101384] [Hero Siege] si_shader: segfault in libLLVM-5.0.so.1
Date: Wed, 28 Jun 2017 16:18:11 +0000 [thread overview]
Message-ID: <bug-101384-502-C19pFh42ag@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101384-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 420 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101384
--- Comment #10 from Christian Lanig <freedesktop@lanig.email> ---
Sorry that it took so long.
I have been able to compile Mesa from git and noticed that the patch has
already been applied. Unfortunately Hero Siege still doesn't run without
dumping both vertex and pixel shaders.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1217 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 prev parent reply other threads:[~2017-06-28 16:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 9:24 [Bug 101384] [Hero Siege] si_shader: segfault in libLLVM-5.0.so.1 bugzilla-daemon
2017-06-12 9:24 ` bugzilla-daemon
2017-06-12 17:29 ` bugzilla-daemon
2017-06-12 18:54 ` bugzilla-daemon
2017-06-12 19:24 ` bugzilla-daemon
2017-06-12 19:56 ` bugzilla-daemon
2017-06-12 20:40 ` bugzilla-daemon
2017-06-12 20:44 ` bugzilla-daemon
2017-06-12 20:45 ` bugzilla-daemon
2017-06-19 11:41 ` bugzilla-daemon
2017-06-19 22:21 ` bugzilla-daemon
2017-06-28 16:18 ` bugzilla-daemon [this message]
2018-03-29 6:32 ` bugzilla-daemon
2018-08-13 14:19 ` bugzilla-daemon
2019-09-25 17:59 ` bugzilla-daemon
2019-09-25 18: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-101384-502-C19pFh42ag@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.