<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 7/22/20 11:34 AM, Jon Chesterfield
via Openmp-dev wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAOUYtQDnZ++u=NHe3esssZj=LukCLwdRSCkV17vhYDtVaV2y_g@mail.gmail.com">
<div dir="ltr">Discovered by accident while looking into a bug for
Ron (cc'd).
<div><br>
</div>
<div>OpenMP running on nvptx defines the __CUDA_ARCH__ macro. Do
we think it should? OpenMP target offloading is somewhat
implemented in terms of cuda but that seems incidental.</div>
</div>
</blockquote>
<p><br>
</p>
<p>Shouldn't it do this only when compiling device code for NVIDIA
architectures?</p>
<p> -Hal<br>
</p>
<p><br>
</p>
<blockquote type="cite" cite="mid:CAOUYtQDnZ++u=NHe3esssZj=LukCLwdRSCkV17vhYDtVaV2y_g@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
<div>I'd like a __GPU_ARCH__ macro which expands to something
useful for nvptx, amdgcn, other. And to not define CUDA_ARCH
when compiling openmp offloading code.</div>
<div><br>
</div>
<div>Thoughts?</div>
<div><br>
</div>
<div>Jon</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<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-signature" cols="72">--
Hal Finkel
Lead, Compiler Technology and Programming Languages
Leadership Computing Facility
Argonne National Laboratory</pre>
</body>
</html>