From: lorn10 <lorn10@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Mesa Clover OpenCL crashes on llvm::TargetInstrInfo::ReplaceTailWithBranchTo()
Date: Thu, 18 May 2023 17:49:45 +0200 [thread overview]
Message-ID: <20230518154945.gjkQvm1Q4pA60EYCA2l8oSPpFaM1OoTeSO1HzYGpBDg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43921@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
New comment by lorn10 on void-packages repository
https://github.com/void-linux/void-packages/issues/43921#issuecomment-1553259426
Comment:
Great!
And it looks that regarding the r600 driver + clover only Mesa MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7357 would be relevant to expose OpenCL 1.2 support. (The other two MRs are radeonsi related.)
In the last comment of [Dave Airlie](https://gitlab.freedesktop.org/airlied) (in Mesa MR 7357) it is noted that that this MR includes as the last piece an improved "AMD LLVM backend patch". Everything other landed in separate commits. Whatever, that Mesa MR 7357 has been stalled for 2 years so it looks that at least a re-base would be needed to get it working again in 2023. :wink:
Long story short, every testing result is of interest especially in regard to rusticl. So please report any relevant result back in Mesa [Tracker Rusticl on r600](https://gitlab.freedesktop.org/mesa/mesa/-/issues/7420). Thanks!
next prev parent reply other threads:[~2023-05-18 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 18:16 [ISSUE] " Mek101
2023-05-18 11:39 ` lorn10
2023-05-18 11:40 ` lorn10
2023-05-18 11:43 ` lorn10
2023-05-18 12:11 ` Mek101
2023-05-18 13:09 ` lorn10
2023-05-18 13:50 ` Mek101
2023-05-18 13:55 ` lorn10
2023-05-18 14:04 ` Mek101
2023-05-18 15:49 ` lorn10
2023-05-18 15:49 ` lorn10 [this message]
2023-05-18 19:43 ` Mek101
2023-05-18 19:44 ` Mek101
2023-05-18 20:39 ` lorn10
2023-05-18 21:11 ` Mek101
2023-05-18 21:14 ` Mek101
2023-05-18 21:16 ` Mek101
2023-05-18 21:19 ` Mek101
2023-05-18 21:23 ` Mek101
2023-05-19 11:45 ` lorn10
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=20230518154945.gjkQvm1Q4pA60EYCA2l8oSPpFaM1OoTeSO1HzYGpBDg@z \
--to=lorn10@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).