From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] [Bug 365] ROCM/Libre-SOC GPU Opcode interoperability
Date: Fri, 12 Jun 2020 22:40:07 +0100
Message-ID: <CAPweEDyRBxMXPUH6Wiq3hpuz_20qGVa3_ayJH=LdNayfEX38dA@mail.gmail.com> (raw)
In-Reply-To: <bug-365-13-CoDR4t23oP@https.bugs.libre-soc.org/>
https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1185925-amd-publishes-video-to-explain-the-radeon-open-compute-stack-rocm?p=1185940#post1185940
:)
On Fri, Jun 12, 2020 at 7:24 PM <bugzilla-daemon@libre-soc.org> wrote:
>
> https://bugs.libre-soc.org/show_bug.cgi?id=365
>
> --- Comment #14 from Jacob Lifshay <programmerjake@gmail.com> ---
> https://www.phoronix.com/scan.php?page=news_item&px=AMD-Video-What-Is-ROCm
>
> --
> 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
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
prev 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
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 [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='CAPweEDyRBxMXPUH6Wiq3hpuz_20qGVa3_ayJH=LdNayfEX38dA@mail.gmail.com' \
--to=lkcl@lkcl.net \
--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