<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/31/2015 06:46 AM, Robinson, Paul
wrote:<br>
</div>
<blockquote
cite="mid:E3B07FDB86BFF041819DC057DEED8FEABDC99A43@USCULXMSG04.am.sony.com"
type="cite">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
debug info generally should be mapping the source to the
code/data as actually generated, even after optimizations
shuffle things around. If the original code thinks it's
allocating something in AS 0 but optimization puts it in AS 3,
and the user asks the debugger to display the value, how does
the debugger know to look in AS 3? Asking the debugger to
troll around looking for an instruction that it might guess is
loading/storing the value and assuming that address is the
actual location… seems like asking a bit much.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--paulr<o:p></o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></a></p>
</blockquote>
It seems like a single attribute for the debug address space isn't
enough then to describe both. I'm fine with just keeping it as the
constant source, and saying that this is one of those optimizations
that destroys hope of sensible debugging. We also have some possible
use cases for non-optimization purposes where an address space ID
would be changed in the backend, but would be an alias for the
original address space. The object isn't literally moved to a
different address space, and is for the backend's benefit so ideally
the user debugging would never be aware that this occurred.<br>
<br>
-Matt<br>
</body>
</html>