From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65085] New: [radeonsi LLVM] Segfault during OpenCL kernel compilation
Date: Tue, 28 May 2013 15:43:05 +0000 [thread overview]
Message-ID: <bug-65085-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65085
Priority: medium
Bug ID: 65085
Assignee: dri-devel@lists.freedesktop.org
Summary: [radeonsi LLVM] Segfault during OpenCL kernel
compilation
Severity: normal
Classification: Unclassified
OS: All
Reporter: niels_ole@salscheider-online.de
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 79901
--> https://bugs.freedesktop.org/attachment.cgi?id=79901&action=edit
Kernel that causes the segfault
I get a segmentation fault in LLVM with Tom Stellard's recent radeonsi compute
patches
(http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20130520/175743.html)
with the attached kernel.
I can work around the issue when executing the if-block in the kernel
unconditionally or with the attached patch to LLVM.
Desc.OpInfo[0].RegClass equals -1 when the segmentation fault occurs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2671 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:[~2013-05-28 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 15:43 bugzilla-daemon [this message]
2013-05-28 15:43 ` [Bug 65085] [radeonsi LLVM] Segfault during OpenCL kernel compilation bugzilla-daemon
2013-05-28 15:44 ` bugzilla-daemon
2013-11-16 2:26 ` 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-65085-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.