<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 14, 2011, at 9:04 PM, Hae-woo Park wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Optima; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>I've met a problem that eliminates a live code in code generation phase.</div><div><br></div><div>The initially generated code is shown as follows (as a pseudo code):</div><div>( Before pseudo-code expansion. )</div><div><br></div><div>----------</div><div>loop:</div><div> :</div><div> :</div><div> set P0 <- xxx ( P0: a physical register for a parameter of function F )</div><div> set P1 <- yyy ( P1: a physical register for a parameter of function F )</div><div> SELECT_CC z1, z2, z3, ...</div><div> ( <- I don't know why this is scheduled at this time,</div><div> however it is independent from function F )</div><div> call F</div><div> :</div><div> :</div><div>----------</div><div><br></div><div>After that, pseudo code expansion stage expands SELECT_CC by slicing the machine basic clock.</div></span></blockquote></div><br><div>I assume you have your own target? I haven't seen this happening with one of the standard targets.</div><div><br></div><div>Your analysis is correct, SELECT_CC shouldn't be scheduled there.</div><div><br></div><div>Normally, LowerCall will create glue edges between the copyToReg SelectionDAG nodes and the CALL node. Is your target not doing that?</div><div><br></div><div>/jakob</div><div><br></div></body></html>