From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105869] [amdgcn/llvm-5] clang crashes when compiling OpenCL kernel
Date: Wed, 09 May 2018 09:29:36 +0000 [thread overview]
Message-ID: <bug-105869-502-USGSrt4ZDq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105869-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 536 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105869
Jan Vesely <jan.vesely@rutgers.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #13 from Jan Vesely <jan.vesely@rutgers.edu> ---
closing per confirmation in comment #12.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2107 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
prev parent reply other threads:[~2018-05-09 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 21:01 [Bug 105869] clang crashes when compiling OpenCL kernel bugzilla-daemon
2018-04-03 21:02 ` bugzilla-daemon
2018-04-04 20:15 ` bugzilla-daemon
2018-04-05 1:20 ` bugzilla-daemon
2018-04-05 12:40 ` bugzilla-daemon
2018-04-05 15:52 ` bugzilla-daemon
2018-04-05 22:00 ` bugzilla-daemon
2018-04-06 1:59 ` bugzilla-daemon
2018-04-06 18:29 ` bugzilla-daemon
2018-04-06 20:35 ` bugzilla-daemon
2018-04-06 20:36 ` bugzilla-daemon
2018-04-06 20:36 ` bugzilla-daemon
2018-05-08 0:31 ` [Bug 105869] [amdgpu/llvm-5] " bugzilla-daemon
2018-05-08 0:31 ` [Bug 105869] [amdgcn/llvm-5] " bugzilla-daemon
2018-05-09 9:26 ` bugzilla-daemon
2018-05-09 9:29 ` bugzilla-daemon [this message]
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-105869-502-USGSrt4ZDq@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).