From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93425] d3dadapter.so (gallium-nine) segfaults since Mesa 11.0/LLVM 3.7
Date: Thu, 17 Dec 2015 17:23:29 +0000 [thread overview]
Message-ID: <bug-93425-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93425
Bug ID: 93425
Summary: d3dadapter.so (gallium-nine) segfaults since Mesa
11.0/LLVM 3.7
Product: Mesa
Version: 11.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: carmenbbakker2@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
On Arch Linux, when using mesa >=11.0 and llvm-libs >=3.7, any use of
gallium-nine segfaults.
The bug is also reported here to the team behind gallium-nine, with more
detailed information: https://github.com/iXit/Mesa-3D/issues/163
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2222 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:[~2015-12-17 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 17:23 bugzilla-daemon [this message]
2015-12-18 20:11 ` [Bug 93425] d3dadapter.so (gallium-nine) segfaults since Mesa 11.0/LLVM 3.7 bugzilla-daemon
2015-12-19 11:12 ` bugzilla-daemon
2015-12-19 11:25 ` bugzilla-daemon
2015-12-19 15:28 ` bugzilla-daemon
2015-12-19 19:31 ` bugzilla-daemon
2015-12-20 3:27 ` bugzilla-daemon
2015-12-20 8:46 ` bugzilla-daemon
2015-12-20 9:07 ` bugzilla-daemon
2015-12-20 13:53 ` 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-93425-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.