<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="text-align:left; direction:ltr;"><div>Hi Lukas,</div><div><br></div><div>Am Mittwoch, den 06.11.2019, 11:20 +0100 schrieb Lukas Sommer:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p>Hi Jonas,</p>
<p>thanks for answer, the command indeed works, I was just missing
the vendor-part of the triple "-unknown" in some places. <br>
</p>
<p>The clang-offload-bundler and the clang linking step seem to be
very sensitive to vendor-part of the target triple. <br>
</p>
<p>[...]</p>
<p>I'm wondering if clang-offload-bundler should be so sensitive to
the vendor-string in the target triple. In particular, if you run
clang with "-fopenmp-targets=x86_64-linux-gnu", you still have to
run clang-offload-bundler with the "unknown" vendor-string,
otherwise the device-part (device.in.ll) will be empty. <br>
</p>
<p>Is this the intended behavior?</p></blockquote><div>Yes, I think it is somewhat intended: Clang normalizes the target triple. As clang-offload-bundler is usually not directly invoked by the user, it just takes the input triple and uses it as a unique key.</div><div>I'm not sure if it would be worth to implement normalization in another tool. Usually, you should be fine if you just copy the commands output by clang -v.</div><div><br></div><div>Regards,</div><div>Jonas</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<p>Thanks,</p>
<p>Lukas<br>
</p>
<pre>Lukas Sommer, M.Sc.</pre><pre>TU Darmstadt</pre><pre>Embedded Systems and Applications Group (ESA)</pre><pre>Hochschulstr. 10, 64289 Darmstadt, Germany</pre><pre>Phone: +49 6151 1622429</pre><pre><a class="moz-txt-link-abbreviated" href="http://www.esa.informatik.tu-darmstadt.de">www.esa.informatik.tu-darmstadt.de</a></pre></blockquote></body></html>