<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Clang silently generates non-working code for GPU targets when passed flags inappropriate for GPUs"
href="https://bugs.llvm.org/show_bug.cgi?id=38979">38979</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Clang silently generates non-working code for GPU targets when passed flags inappropriate for GPUs
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>6.0
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>OpenCL
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>infinity0@debian.org
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Debian adds "-fstack-protector-strong" to CFLAGS for all packages.
Unfortunately one of our maintainers was a bit overzealous in applying that
manually to libclc's build files which causes it to fail when compiling opencl
code at runtime.
What was less clear whether the concept of a stack protector makes sense for
GPU code. Either way Clang needs a fix - (a) if it doesn't make sense, then
Clang should fail when the flag is given, or at least warn and not generate
incorrect code; (b) if it does make sense, then Clang should be fixed to
generate correct and working code.
Please see the freedesktop.org bug report linked below, for a dump of the code
being generated and more details.
<a href="https://bugs.freedesktop.org/show_bug.cgi?id=107369">https://bugs.freedesktop.org/show_bug.cgi?id=107369</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>