<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/30/2015 01:59 PM, David Blaikie
wrote:<br>
</div>
<blockquote
cite="mid:CAENS6EsRuRRY5ZU5OXcGFf=MB7tRfiMoNZ6KVb8M7aqiKUgeDg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jul 30, 2015 at 1:41 PM, Matt
Arsenault <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:Matthew.Arsenault@amd.com" target="_blank">Matthew.Arsenault@amd.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 07/30/2015 10:54 AM, David Blaikie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
If we could rely on the llvm::Value that the debug
info variable description points to always having a
PointerType with the desired address space, then we
could just get it from there & wouldn't need to
add more info to the debug info variable description.<br>
</blockquote>
</span>
OK, I see what you mean now. We would like to be able to
change the address space of the value for optimization
purposes, but still report the source address space. For
example, the AMDGPUPromoteAlloca pass now currently tries
to replace allocas in address space 0 with globals in
address space 3.<br>
</blockquote>
<div><br>
</div>
<div>Interesting - what's the debugger going to do with the
address space, though? Is it going to need to know the
real address space, or the original one?</div>
<div> </div>
</div>
<br>
</div>
</div>
</blockquote>
I would expect the debugger to show the original address space. If
it needed to know the address space of the actual load / store, it
could look at what machine instruction is being executed.<br>
<br>
I'm trying to add addrSpace as a first class member of DIDerivedType
like SizeInBits/AlignInBits, but this seems to require touching more
components than I expected. Does this field really need to be added
to MDNodeKeyImpl? This seems like a lower level place than I
expected needing to touch. I would expect people would want to avoid
adding new fields to things like this to save memory<br>
<br>
-Matt<br>
</body>
</html>