<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 Oct 8, 2020, at 4:07 AM, Tozer, Stephen <<a href="mailto:stephen.tozer@sony.com" class="">stephen.tozer@sony.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><br class="Apple-interchange-newline">> So I wonder if we should instead model this only at the MIR level, where this distinction actually makes sense. In MIR, we probably don't want to rewrite every DIExpression, so it would make sense to model it either as a flag on the intrinsic, or by have two kinds of intrinsics.<br class=""></div><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><br class=""></div><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">That works for me - as long as we have the ability to represent these expressions, it should be fine. What will be slightly awkward is maintaining this at the same time as the old DBG_VALUE; having two flags on two different but related instructions with the same name and meanings that are almost the same but slightly different. Still, the old version will be deprecated so we shouldn't have to worry too much.</div></div></blockquote><br class=""></div><div>My expectation is that DBG_VALUE_OLD is not going to stick around with us for very long. It's only used internally in LLVM and we should be able to move off it quickly. That the short transitional period may be confusing doesn't bother me.</div><div><br class=""></div><div>Great — that sounds like a plan then!</div><div><br class=""></div><div>thanks for your patience working through this,</div><div>adrian</div></body></html>