<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<p style="font-family:Arial;font-size:10pt;color:#0000FF;margin:5pt;" align="Left">
[AMD Official Use Only]<br>
</p>
<br>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Re-iterating the proposed change and clarifying the concerns raised :
<div><br>
</div>
<div>Proposed change:</div>
<div>- Allow no-op bitcast between pointers of same size but from different addrspaces.</div>
<div><br>
</div>
<div>Clarifying the concerns:</div>
<div>- No-op reinterprent of bits between addrspaces is already done in the IR like introducing ptrtoint/inttoptr(ex. GVN).</div>
<div> Main motivation for this change is to give the IR a way to represent a cast we know is a no-op without resorting to ptrtoint/inttoptr.
</div>
<div><br>
</div>
<div>- With this change we do not want to introduce new illegal address space conversions that were not already present in the original program.</div>
<div> The original code was not performing an address space cast, it was doing type punning and reinterpreting some bits as a different address space.</div>
<div> It was broken to begin with if the target didn't allow no-op conversions between given pair of address spaces. We are not intending to change that. </div>
<div> Since the IR transform like in GVN case, did a no-op reinterpretation of bits between addrspaces, We are just trying to optimise it by using a no-op bitcast.</div>
<div><br>
</div>
<div>- Since the original IR already did this reinterpret of bits without querying the target, the change we propose will also not query the target.
</div>
<div> This pointer-reinterpret-to-cast transformation is and should be done unconditionally. Querying TTI to check for no-op would introduce target dependence on Core IR instruction semantics.</div>
<div> We used DataLayout to match the pointer sizes. This check is sufficient to allow the no-op bitcast.
</div>
<div><br>
</div>
<div>- Also, there is no target specific pattern to search for here. Irrespective of the target, we need to introduce new IR that represents the same no-op reinterpret of bits between addrspaces.</div>
<div> All the targets are intended to benefit from this change.</div>
<div><br>
</div>
<div>Regards,</div>
Chaitanya<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Matt Arsenault <whatmannerofburgeristhis@gmail.com> on behalf of Matt Arsenault <arsenm2@gmail.com><br>
<b>Sent:</b> 01 December 2021 05:57<br>
<b>To:</b> Renato Golin <rengolin@gmail.com><br>
<b>Cc:</b> Sankisa, Krishna (Chaitanya) <Krishna.Sankisa@amd.com>; llvm-dev@lists.llvm.org <llvm-dev@lists.llvm.org><br>
<b>Subject:</b> Re: [llvm-dev] [RFC] : LLVM IR should allow bitcast between address spaces with the same size</font>
<div> </div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">[CAUTION: External Email]
<div><br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Nov 30, 2021, at 04:51, Renato Golin <<a href="mailto:rengolin@gmail.com" class="">rengolin@gmail.com</a>> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">On Mon, 29 Nov 2021 at 18:15, Matt Arsenault <<a href="mailto:arsenm2@gmail.com" target="_blank" class="">arsenm2@gmail.com</a>> wrote:<br class="">
</div>
<div class="x_gmail_quote">
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
<div class="">
<div class="">
<div class="">This is true, but this isn’t directly related to this change. If the target does not have no-op conversions between a given pair of address spaces, the original code was broken to begin with. This change does not allow introducing new illegal
address space conversions that were not already present in the original program. It’s garbage in, garbage out. If the target can’t really reinterpret these pointers, it would be UB on access.</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Ah, I see.</div>
<div class=""><br class="">
</div>
<div class="">So IIUC, adding the casts in the first place would have to know about target address spaces, but this specific change only allows eliding the inttoptr cast in the specific case where the address spaces have the same data layout?</div>
<div class=""><br class="">
</div>
<div class="">Assuming the initial cast was legal to begin with, this looks sensible to me.</div>
</div>
</div>
</div>
</blockquote>
<div>The target’s notion of address space casts doesn’t apply here. The user decided to reinterpret the pointer in a different address space, which may or may not be valid to use on the target.</div>
<div><br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="x_gmail_quote">
<div class=""><br class="">
</div>
<div class="">I was worried this would allow (encourage?) front-ends and other passes to add an address space cast where none (could have) existed in the first place.</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>No, we’re converting from an in-memory representation of reinterpreting bits to one in values. Frontends still need to have some contextual knowledge of what the language and target expects out of address spaces. </div>
<div><br class="">
</div>
</div>
<div class="">-Matt</div>
</div>
</div>
</div>
</body>
</html>