<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 21, 2019, at 11:14 AM, James Y Knight <<a href="mailto:jyknight@google.com" class="">jyknight@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class="">If an asm's constraints claim that the variable is an output, but then don't actually write to it, that's a bug (at least if the value is actually used afterwards). An output-only constraint on inline asm definitely does _not_ mean "pass through the previous value unchanged, if the asm failed to actually write to it". If you need that behavior, it's spelled "+m", not "=m".<br class=""></div><div class=""><br class=""></div><div class="">We do seem to fail to take advantage of this for memory outputs (again, this is not just for ftrivial-auto-var-init -- we ought to eliminate manual initialization just the same), which I'd definitely consider an missing-optimization bug.</div></div></div></div></blockquote><div><br class=""></div><div>Agreed on both counts. Maybe we don’t do the optimization because code tends to be wrong? If that’s the case, the optimization would make people sad (even though their code is wrong). We might need to validate asm statement constraints…</div><div><br class=""></div><div>I don’t want us to just blindly do the optimization and break code, even if said code was incorrect.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 21, 2019 at 10:16 AM Alexander Potapenko <<a href="mailto:glider@google.com" class="">glider@google.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Mar 21, 2019 at 2:58 PM James Y Knight <<a href="mailto:jyknight@google.com" target="_blank" class="">jyknight@google.com</a>> wrote:<br class="">
><br class="">
> Please be more specific about the problem, because your simplified example doesn't actually show an issue. If I write this function:<br class="">
> int foo() {<br class="">
> int retval;<br class="">
> asm("# ..." : "=r"(retval));<br class="">
> return retval;<br class="">
> }<br class="">
> it already does get treated as definitely writing retval, and optimizes away the initialization (whether you explicitly initialize retval, or use -ftrivial-auto-var-init).<br class="">
> Example: <a href="https://godbolt.org/z/YYBCXL" rel="noreferrer" target="_blank" class="">https://godbolt.org/z/YYBCXL</a><br class="">
This is probably because you're passing retval as a register output.<br class="">
If you change "=r" to "=m" (<a href="https://godbolt.org/z/ulxSgx" rel="noreferrer" target="_blank" class="">https://godbolt.org/z/ulxSgx</a>), it won't be<br class="">
optimized away.<br class="">
(I admit I didn't know about the difference)<br class="">
> On Thu, Mar 21, 2019 at 8:35 AM Alexander Potapenko via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>> wrote:<br class="">
>><br class="">
>> Hi JF et al.,<br class="">
>><br class="">
>> In the Linux kernel we often encounter the following pattern:<br class="">
>><br class="">
>> type op(...) {<br class="">
>> type retval;<br class="">
>> inline asm(... retval ...);<br class="">
>> return retval;<br class="">
>> }<br class="">
>><br class="">
>> , which is used to implement low-level platform-dependent memory operations.<br class="">
>><br class="">
>> Some of these operations turn out to be very hot, so we probably don't<br class="">
>> want to initialize |retval| given that it's always initialized in the<br class="">
>> assembly.<br class="">
>><br class="">
>> However it's practically impossible to tell that a variable is being<br class="">
>> written to by the inline assembly, or figure out the size of that<br class="">
>> write.<br class="">
>> Perhaps we could speculatively treat every scalar output of an inline<br class="">
>> assembly routine as an initialized value (which is true for the Linux<br class="">
>> kernel, but I'm not sure about other users of inline assembly, e.g.<br class="">
>> video codecs).<br class="">
>><br class="">
>> WDYT?<br class="">
>><br class="">
>><br class="">
>> --<br class="">
>> Alexander Potapenko<br class="">
>> Software Engineer<br class="">
>><br class="">
>> Google Germany GmbH<br class="">
>> Erika-Mann-Straße, 33<br class="">
>> 80636 München<br class="">
>><br class="">
>> Geschäftsführer: Paul Manicle, Halimah DeLaine Prado<br class="">
>> Registergericht und -nummer: Hamburg, HRB 86891<br class="">
>> Sitz der Gesellschaft: Hamburg<br class="">
>> _______________________________________________<br class="">
>> cfe-dev mailing list<br class="">
>> <a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a><br class="">
>> <a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class="">
<br class="">
<br class="">
<br class="">
--<br class="">
Alexander Potapenko<br class="">
Software Engineer<br class="">
<br class="">
Google Germany GmbH<br class="">
Erika-Mann-Straße, 33<br class="">
80636 München<br class="">
<br class="">
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado<br class="">
Registergericht und -nummer: Hamburg, HRB 86891<br class="">
Sitz der Gesellschaft: Hamburg<br class="">
</blockquote></div>
</div></blockquote></div><br class=""></body></html>