Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 365] ROCM/Libre-SOC GPU Opcode interoperability
Date: Sun, 07 Jun 2020 20:29:52 +0000
Message-ID: <bug-365-13-JGrsVk1N07@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-365-13@https.bugs.libre-soc.org/>

https://bugs.libre-soc.org/show_bug.cgi?id=365

--- Comment #10 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jacob Lifshay from comment #7)
> From what I understand, ROCm is only for OpenCL/CUDA-style compute, it
> doesn't implement the Vulkan or OpenGL APIs:
> https://github.com/RadeonOpenCompute/ROCm/issues/706
> https://github.com/RadeonOpenCompute/ROCm/issues/131

(In reply to Luke Kenneth Casson Leighton from comment #8)
> https://gpuopen.com/gpuperfapi/
> 
> that's interesting. Version 3.5 (dec 2019):
> "Remove ROCm/HSA support."

Can you clarify the purpose of the present investigation for me? 

Are we trying to find out if we can use the many man-years of development put
into the Radeon Open Compute Stack by making minimal modifications to our
external graphics api to make it compatible with HSA/ROCM?

Is HSA general across all radeon gpus? I remember reading that HSA was an
abstraction specific to only two of AMD's APUs

Are we looking not so much for OpenCL support, but instead the graphics stack
for OpenGL, Vulkan, DirectX, etc?

Or are we looking for both Compute and Graphics?

Would we take the route of making a fork of clang/llvm specific to Libre-SOC,
and trying to have these changes upstreamed to clang/llvm trunk?

All of these questions are asked in near total ignorance.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-06 23:57 [libre-riscv-dev] [Bug 365] New: " bugzilla-daemon
2020-06-06 23:58 ` [libre-riscv-dev] [Bug 365] " bugzilla-daemon
2020-06-07  2:50 ` bugzilla-daemon
2020-06-07  3:03 ` bugzilla-daemon
2020-06-07  3:31 ` bugzilla-daemon
2020-06-07  3:47 ` bugzilla-daemon
2020-06-07  4:30 ` bugzilla-daemon
2020-06-07 17:41 ` bugzilla-daemon
2020-06-07 17:52 ` bugzilla-daemon
2020-06-07 20:21 ` bugzilla-daemon
2020-06-07 20:29 ` bugzilla-daemon [this message]
2020-06-07 21:23 ` bugzilla-daemon
2020-06-07 21:39 ` bugzilla-daemon
2020-06-09 17:04 ` bugzilla-daemon
2020-06-12 18:24 ` bugzilla-daemon
2020-06-12 21:40   ` Luke Kenneth Casson Leighton

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-365-13-JGrsVk1N07@https.bugs.libre-soc.org/ \
    --to=bugzilla-daemon@libre-soc.org \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git