From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105950] radeonsi: OpenCL not working correctly on a big endian machine
Date: Mon, 09 Apr 2018 10:52:17 +0000 [thread overview]
Message-ID: <bug-105950-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105950
Bug ID: 105950
Summary: radeonsi: OpenCL not working correctly on a big endian
machine
Product: Mesa
Version: 17.3
Hardware: PowerPC
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: bas@daedalean.ai
QA Contact: dri-devel@lists.freedesktop.org
Running any OpenCL program on a big endian machine using a radeonsi card fails.
- union si_vgt_param_key uses a bitfield shared with a 32 bit value. This
causes the index to be wrong on a big endian machine, and crashes any OpenCL
program with a segfault.
- si_setup_user_sgprs_co_v2 in si_compute.c fills a dispatch_packet struct with
values which are uploaded to the GPU. To ensure this works correctly, these
values need to be converted to little endian.
I'll send patches to the mesa-dev list for both these issues.
Bas Vermeulen
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2568 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
next reply other threads:[~2018-04-09 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 10:52 bugzilla-daemon [this message]
2018-04-09 11:16 ` [Bug 105950] radeonsi: OpenCL not working correctly on a big endian machine bugzilla-daemon
2018-04-09 11:17 ` bugzilla-daemon
2018-09-09 22:43 ` 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-105950-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.