<html>
<head>
<base href="https://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 - [llvm-mca] Make the pipeline configurable."
href="https://bugs.llvm.org/show_bug.cgi?id=36663">36663</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[llvm-mca] Make the pipeline configurable.
</td>
</tr>
<tr>
<th>Product</th>
<td>new-bugs
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</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>new bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>courbet@google.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>Following my comment on the initial review:
<a href="https://reviews.llvm.org/D43951?id=136547#inline-384487">https://reviews.llvm.org/D43951?id=136547#inline-384487</a>
There is a lot of coupling between the driver
(RunCycle()/NotifyCycleBegin()/NotifyCycleEnd()) and the pipeline itself. This
should be split into a driver class ad a configurable pipeline.
With the current design the backend has to know about all the possible
pipelines and expose all the quantities that listeners might be interested in
(GetNumXXXStalls(), NotifyInstructionXXX()). This does not scale well to more
pipeline components (in particular to simulate the frontend). I think it would
be better to manipulate IB/HWS/DU though a common interface and give this
interface a way to notify the listeners.</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>