dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93370] [clover/caicos] OpenCL atomic_cmpxchg() segmentation fault
Date: Wed, 30 May 2018 14:01:25 +0000	[thread overview]
Message-ID: <bug-93370-502-cM7BdBvPsm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93370-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93370

Jan Vesely <jan.vesely@rutgers.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[r600g] OpenCL              |[clover/caicos] OpenCL
                   |atomic_cmpxchg()            |atomic_cmpxchg()
                   |segmentation fault on       |segmentation fault
                   |Caicos                      |

--- Comment #1 from Jan Vesely <jan.vesely@rutgers.edu> ---
The backtrace does not look compilation related.
However, atomic ops that return the old value are not supported atm.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1998 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

  parent reply	other threads:[~2018-05-30 14:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 15:59 [Bug 93370] [r600g] OpenCL atomic_cmpxchg() segmentation fault on Caicos bugzilla-daemon
2017-01-31 13:01 ` bugzilla-daemon
2018-05-30 14:01 ` bugzilla-daemon [this message]
2019-09-18 19:20 ` [Bug 93370] [clover/caicos] OpenCL atomic_cmpxchg() segmentation fault 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-93370-502-cM7BdBvPsm@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