From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76223] [radeonsi] luxmark segfault
Date: Wed, 02 Jul 2014 21:33:17 +0000 [thread overview]
Message-ID: <bug-76223-502-jNHAh9XvK7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76223-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76223
--- Comment #13 from Aaron Watry <awatry@gmail.com> ---
Created attachment 102163
--> https://bugs.freedesktop.org/attachment.cgi?id=102163&action=edit
Possible fix for luxmark segfault
The luxrays kernels used an __attribute__(work_group_size_hint(64,1,1)) on
several kernels. Mesa was not expecting kernels to have multiple operands in
the LLVM metadata nodes (and an attribute is represented as an additional
metadata node). This led to memory corruption and an LLVM error.
This patch fixes the piglit test case in attachment 101832 on CEDAR (r600g),
and it probably helps radeonsi as well (which I can test later).
This same patch will be sent to the mesa-dev list momentarily.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2055 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-07-02 21:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 5:23 [Bug 76223] New: [radeonsi] luxmark segfault bugzilla-daemon
2014-03-21 14:19 ` [Bug 76223] " bugzilla-daemon
2014-03-22 6:08 ` bugzilla-daemon
2014-03-23 5:00 ` bugzilla-daemon
2014-06-08 18:05 ` bugzilla-daemon
2014-06-09 18:16 ` bugzilla-daemon
2014-06-09 18:18 ` bugzilla-daemon
2014-06-11 23:39 ` bugzilla-daemon
2014-06-17 16:05 ` bugzilla-daemon
2014-06-18 21:18 ` bugzilla-daemon
2014-06-18 21:19 ` bugzilla-daemon
2014-06-18 21:21 ` bugzilla-daemon
2014-06-27 0:44 ` bugzilla-daemon
2014-07-02 21:33 ` bugzilla-daemon [this message]
2015-01-24 8:29 ` bugzilla-daemon
2015-01-24 10:57 ` bugzilla-daemon
2015-01-31 15:18 ` bugzilla-daemon
2015-02-01 20:33 ` bugzilla-daemon
2015-02-05 6:03 ` bugzilla-daemon
2015-02-05 14:35 ` bugzilla-daemon
2015-02-07 7:34 ` bugzilla-daemon
2015-02-09 3:46 ` bugzilla-daemon
2015-02-09 5:26 ` bugzilla-daemon
2015-02-09 6:14 ` bugzilla-daemon
2015-02-10 5:15 ` bugzilla-daemon
2015-02-10 6:28 ` bugzilla-daemon
2015-02-21 5:28 ` 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-76223-502-jNHAh9XvK7@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;
as well as URLs for NNTP newsgroup(s).