Andreas Herten

[![](/assets/img/posts/2024-06-12-p3hpc-compat/table.png){srcset="/assets/img/posts/2024-06-12-p3hpc-compat/table.png 1x, /assets/img/posts/2024-06-12-p3hpc-compat/table.2x.png 2x"}](/models/)

In [November of 2022](/2022/11/02/gpu-vendor-model-compat.html), I
created a table comparing GPU programming models and their support on
GPUs of the three vendors (AMD, Intel, NVIDIA) for a talk. The audience
liked it, so I beefed it up a little and posted it in this very blog.

People [**still** liked
it](https://scholar.google.de/scholar?oi=bibs&hl=de&cites=8160066363790021249),
so I took opportunity of some downtime to update and significantly
extend it, and make it into a paper for the [SC23 Workshop on
*Performance, Portability and Productivity in
HPC*](https://p3hpc.org/workshop/2023/) ([P3HPC](https://p3hpc.org/)).
In November 2023, [the paper was published as part of the SC23 Workshop
Proceedings](https://dl.acm.org/doi/10.1145/3624062.3624178?cid=99659740494).
Because it's closed access, you can access it freely if you come from
this blog^[1](#fn:authorizer){.footnote rel="footnote"}^; alternatively,
check out [the
preprint](https://arxiv.org/abs/2309.05445)^[2](#fn:perfectionism){.footnote
rel="footnote"}^.  
I also created a dedicated [*Models page* here on the blog](/models/),
which has the content in HTML form -- and also includes the link to the
paper.

I've changed the following things, compared to the original blog post:

1.  Update all entries and check for additions, deprecations, and other
    developments; extend the descriptions
2.  Describe more properly the methods and categories
3.  Add references for each entry, usually referring to the tool or
    specific aspect discussed
4.  Add discussions and a conclusion
5.  Keep the [GitHub repo](https://github.com/AndiH/gpu-lang-compat) as
    the single source of truth, but extend it to generate the PDF paper
    and to include references in the HTML version (through some horrible
    Pandoc trickery^[3](#fn:pandoctrickery){.footnote rel="footnote"}^)

As the paper is by no means *finished* but a mere snapshot of the status
quo in November 2023, my mini-presentation at the P3HPC workshop
(embedded below) asked for help from the community to keep the content
up-to-date; in the form of contributions to the [GitHub
repository](https://github.com/AndiH/gpu-lang-compat).  
So, **please help** [keep the content
up-to-date](https://github.com/AndiH/gpu-lang-compat/issues)! All
included updates will be incorporated immediately into the [*Models*
page](/models/), the new home of the table. In case you ever forget, the
table and repository are also linked [from the P3HPC workshop
website](https://p3hpc.org/resources/).

Your browser is unable to display the PDF. Instead, please [download
it](/assets/slides/posts/2024-06-12-p3hpc-compat/aherten-p3phpc-mcmm.pdf).

::: {.footnotes role="doc-endnotes"}
1.  ::: {#fn:authorizer}
    ACM gives authors the opportunity to add two referring domains to an
    *accept list*, which displays the paper despite closed access. Not
    great, but better than
    nothing. [↩](#fnref:authorizer){.reversefootnote
    role="doc-backlink"}
    :::

2.  ::: {#fn:perfectionism}
    While I have you here, let me talk about TeX. I've created the PDF
    following the SC23 ACM template guidelines. The most elaborate
    TeXing is some TikZ sprinkled here and there. For the literature, I
    used BibLaTeX, as per ACM's guidelines. Now, first, arXiv has issues
    with the two-column layout and stumbles over hyphenating words for
    line breaks. I could fix most, but not all. Then, for the actual
    publishing, turns out thath the publisher can not even accept
    BibLaTeX, but needs BibTeX. Because I use a lot of URLs and the
    appropriate fields in the bib file, I needed to rework this
    extensively -- last-minute and with a less pleasing look. So while
    the arXiv version still contains BibLaTeX (but has hyphenation
    issues), the published version has BibTeX (but no hyphenation
    issues). [A locally generated pre-preprint with proper hyphenation
    and bibliography can be found here for
    reference](/assets/misc/posts/2024-06-12-p3hpc-compat/aherten-p3hpc-gpu-compat.pdf).
    Phew. [↩](#fnref:perfectionism){.reversefootnote
    role="doc-backlink"}
    :::

3.  ::: {#fn:pandoctrickery}
    References can be referred to by multiple entries, of course, so
    just adding a reference behind each explaining entry would create a
    lot of duplications. To resolve that, I basically concatenate all
    references in a long, Markdown-formatted string and convert it to
    HTML with Pandoc, letting Pandoc resolve the dependencies. I then
    parse the HTML string again to extract the references for each table
    entry in HTML form and add them to the
    output. [↩](#fnref:pandoctrickery){.reversefootnote
    role="doc-backlink"}
    :::
:::


In November of 2022, I created a table comparing GPU programming models and their  support on GPUs of the three vendors (AMD, Intel, NVIDIA) for a talk. The audience liked it, so I beefed it up a little and posted it in this very blog.

Publicaciones de Rogue Scholar

Paper: Many Cores, Many Models – GPU Programming Model vs. Vendor Compatibility Overview