<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Oct 2, 2013, at 3:21 PM, Hal Finkel <<a href="mailto:hfinkel@anl.gov">hfinkel@anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">What would be really quite useful is if we had the scheduler tag the MIs with their expected dispatch latency (meaning number of stall cycles for an in-order core), and printed that in the assembly output.</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div><br><div>It would be nice. There are two approaches.</div><div><br></div><div>- Implement a pipeline model outside of CodeGen. That’s good for stand alone tools, along the lines of Quentin’s work.</div><div><br></div><div>- Implement something like Daniel Malea’s debugIR at MI level so the scheduler (and other passes) can dump a bunch of diagnostics tied to dwarf line numbers.</div><div><br></div><div>-Andy</div></body></html>