<html>
<head>
<base href="http://bugs.llvm.org/">
</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 - ScopDetection::isMaxRegionInScop updates DetectionContext, but does not need to invalidate it."
href="http://bugs.llvm.org/show_bug.cgi?id=32519">32519</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>ScopDetection::isMaxRegionInScop updates DetectionContext, but does not need to invalidate it.
</td>
</tr>
<tr>
<th>Product</th>
<td>Polly
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Other
</td>
</tr>
<tr>
<th>Assignee</th>
<td>polly-dev@googlegroups.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>llvm@meinersbur.de
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>The method ScopDetection::isMaxRegionInScop() is supposed to find out whether a
region is still a valid SCoP after code generation of another. This is tested
by test\Isl\CodeGen\multiple-scops-in-a-row.ll.
As a side-effect of this check, it also updates the DetectionContext. After
this update multiple-scops-in-a-row.ll is again a valid SCoP. Logically,
code-generation of another SCoP should never invalidate another. However, it
remains an invalid SCoP in the following LLVM test-suite programs:
External/Povray/povray
External/SPEC/CINT2006/400.perlbench/400.perlbench
MultiSource/Applications/lemon/lemon
MultiSource/Benchmarks/MallocBench/cfrac/cfrac
MultiSource/Benchmarks/Prolangs-C/TimberWolfMC/timberwolfmc
MultiSource/Benchmarks/mafft/pairlocalalign
SingleSource/Benchmarks/Polybench/linear-algebra/solvers/gramschmidt/gramschmidt
This update of DetectionContext should be explicit, not in isMaxRegionInScop()
which should be side-effect-free.
Ideally, we identify the reason why some SCoPs are not valid SCoPs after code
generation anymore and fix this.</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>