Github messages for voidlinux
 help / color / mirror / Atom feed
From: Mek101 <Mek101@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Mesa Clover OpenCL crashes on llvm::TargetInstrInfo::ReplaceTailWithBranchTo() 
Date: Wed, 17 May 2023 20:16:29 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43921@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

New issue by Mek101 on void-packages repository

https://github.com/void-linux/void-packages/issues/43921

Description:
### Is this a new report?

Yes

### System Info

Void 6.2.15_1 x86_64 AuthenticAMD notuptodate rrFFFF

### Package(s) Affected

mesa-22.3.5_2 mesa-opencl-22.3.5_2 libllvm15-15.0.7_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The system should run the Tensorflow model with OpenCL 1.1

### Actual behaviour

Running some models causes the OpenCL implementation (Mesa's Clover) to call `llvm::TargetInstrInfo::ReplaceTailWithBranchTo()` from `/usr/lib/libLLVM-15.so`, which itself is provided by the `libllvm15` package. This function call causes a segmentation fault (verified via `gdb`).

### Steps to reproduce

- Ensure Mesa uses Clover as an OpenCL implementation
- Donwload an affected TensorFlow Lite model (at least `squeezenet` in my case)
- Compile TensorFlow Lite's benchmark with GPU support.
- Run it with the `--use_gpu=true --gpu_backend="cl"` options.
- Observe the segmentation fault

In my particular case I'm using an old Radeon 8670D, a Terascale 3 iGPU with the `radeon` kernel driver.

Squeezenet: https://tfhub.dev/tensorflow/lite-model/squeezenet/1/default/1

             reply	other threads:[~2023-05-17 18:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 18:16 Mek101 [this message]
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

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43921@inbox.vuxu.org \
    --to=mek101@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).