From: lorn10 <lorn10@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Mesa Clover OpenCL crashes on llvm::TargetInstrInfo::ReplaceTailWithBranchTo()
Date: Fri, 19 May 2023 13:45:13 +0200 [thread overview]
Message-ID: <20230519114513.LZIsJrV1kFu8Rsb9OpzIDTOn51973oBMxIoNxUthz1I@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: 789 bytes --]
New comment by lorn10 on void-packages repository
https://github.com/void-linux/void-packages/issues/43921#issuecomment-1554451077
Comment:
> It seems that the only changes in the commit are those for a printf support?
Yes, that's exactly the last thing (on Radeon GPUs) which is/was missing to advertise full OpenCL 1.2 support in clover. :+1:
> I can't find it in the repos
Okay, then it is not avaiable in the void Linux repos. On Debian/Ubuntu it is present so I have only to enter:
`sudo apt install clpeak`
or
`sudo snap install clpeak`
Whatever, - thanks for testing! And maybe you open a new bug report on the [llvm-project issue tracker](https://github.com/llvm/llvm-project/issues) about the `llvm::TargetInstrInfo::ReplaceTailWithBranchTo()` error. :wink:
prev parent reply other threads:[~2023-05-19 11:45 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
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 [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=20230519114513.LZIsJrV1kFu8Rsb9OpzIDTOn51973oBMxIoNxUthz1I@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).