<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW " title="NEW --- - Consider emitting all variables in collectVariableInfo(), even ones with no ranges" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__llvm.org_bugs_show-5Fbug.cgi-3Fid-3D23908&d=AwMBaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=pF93YEPyB-J_PERP4DUZOJDzFVX5ZQ57vQk33wu0vio&m=30WU93j0A5HOpYpLBhpXKM8KFb9LMhfgPSaO4k7EAbg&s=zButd4XbryMcFe7Pmkgt8z2nhfZkZrnkfRY4byEhz28&e=">23908</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Consider emitting all variables in collectVariableInfo(), even ones with no ranges
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>DebugInfo
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>dexonsmith@apple.com
</td>
</tr>
<tr>
<th>CC</th>
<td>aprantl@apple.com, dblaikie@gmail.com, llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>If a variable in `DbgValues` has no ranges, we currently don't emit it. In the
review thread leading to r240244, David and Adrian suggested that we should
emit it anyway. As an example of why, consider:
int foo(int f) {
if (bar()) {
bool f = false;
// ...
}
// ...
}
If the local variable `f` is optimized out, the debugger should still "know"
about it. Otherwise, evaluating `expression f` when stepping through the `if`
statement will refer to the parameter.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>