<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - "volatile" in OpenCL code not recognized by POLARIS10 and KABINI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107369#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - "volatile" in OpenCL code not recognized by POLARIS10 and KABINI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107369">bug 107369</a>
from <span class="vcard"><a class="email" href="mailto:infinity0@pwned.gg" title="infinity0@pwned.gg">infinity0@pwned.gg</a>
</span></b>
<pre>For background, this is the CFLAGS that Debian passes when compiling all C
programs. From the GCC man page:
-fstack-protector
Emit extra code to check for buffer overflows, such as stack smashing
attacks. This is done by adding a guard variable to functions with
vulnerable objects. This includes functions that call "alloca", and
functions with buffers larger than 8 bytes. The guards are initialized when
a function is entered and then checked when the function exits. If a guard
check fails, an error message is printed and the program exits.
-fstack-protector-strong
Like -fstack-protector but includes additional functions to be protected ---
those that have local array definitions, or have references to local frame
addresses.
Of course GPUs are different so this may not be appropriate. I'm not familiar
with how OpenCLs work so please confirm what the most appropriate solution is
for Debian, either:
- append -fno-stack-protector to the Debian flags, if the other flags are
appropriate/relevant here
- omit all the flags completely and leave clang_bc_flags alone, if this is such
a special thing that Debian's system-policy CFLAGS should be completely ignored</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>