<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Hack Nerd Font Mono">Sure :) That is the
proposal/patch.</font></p>
<p><font face="Hack Nerd Font Mono"></font><br>
</p>
<div class="moz-cite-prefix">On 7/9/20 10:02 AM, Alexey.Bataev
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:VE1PR09MB34085AF351E56AA70366DD0196640@VE1PR09MB3408.eurprd09.prod.outlook.com">
<pre class="moz-quote-pre" wrap="">You need to to remove the paramater from the runtime function, i.e. need
to modify deviceRTL
-------------
Best regards,
Alexey Bataev
09.07.2020 10:58 AM, Johannes Doerfert via Openmp-dev пишет:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I'll go ahead with the patches today.
What do you mean by fix the runtime part first?
~ Johannes
On 7/9/20 7:18 AM, Alexey.Bataev wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">If there are no objections, it is good to go. Just fix the runtime part
at first.
-------------
Best regards,
Alexey Bataev
07.07.2020 10:57 AM, Johannes Doerfert пишет:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">As part of a patch to remove dead arguments [0] a discussion started
which asked for an RFC [1].
--
I want to clarify that there is no guarantee the *device runtime*
(aka. libomptarget-nvptx-sm_XX.bc) has a stable API.
Quick summary of the discussion:
- The library in question is *not* part of libomp (which has a stable
API) or even libomptarget.
- We are not aware of any non-clang user of this library.
- The only usage model we (properly) support is static linking of the
runtime as LLVM-IR. This inherently ties the runtime to the compiler
(version):
- Combining a new compiler with an old (LLVM-IR) runtime cannot be
expected to work as we might have new entry points.
- Combining an old compiler with a new (LLVM-IR) runtime cannot be
expected to work as we cannot guarantee the old toolchain can handle
the new IR .
Please provide feedback asap, this is a requirement for the GPU state
machine patch [2] which fixes an important register usage bug [3].
Thanks,
Johannes
[0] <a class="moz-txt-link-freetext" href="https://reviews.llvm.org/D83268">https://reviews.llvm.org/D83268</a>
[1] <a class="moz-txt-link-freetext" href="https://reviews.llvm.org/D83268#2136060">https://reviews.llvm.org/D83268#2136060</a>
[2] <a class="moz-txt-link-freetext" href="https://reviews.llvm.org/D83271">https://reviews.llvm.org/D83271</a>
[3] <a class="moz-txt-link-freetext" href="http://llvm.org/PR46450">http://llvm.org/PR46450</a>
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Openmp-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openmp-dev@lists.llvm.org">Openmp-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</body>
</html>