<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 23, 2009, at 9:16 AM, Dan Gohman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; ">Author: djg<br>Date: Mon Nov 23 11:16:22 2009<br>New Revision: 89667<br><br>URL:<span class="Apple-converted-space"> </span><a href="http://llvm.org/viewvc/llvm-project?rev=89667&view=rev">http://llvm.org/viewvc/llvm-project?rev=89667&view=rev</a><br>Log:<br>Move the FunctionLoweringInfo class and some related utility functions out<br>of SelectionDAGBuild.h/cpp into its own files, to help separate<br>general lowering logic from SelectionDAG-specific lowering logic.</span></blockquote></div><br><div>Hi Dan,</div><div><br></div><div>Would it make sense to split TargetLowering into TargetLowering and SDLowering classes? The former would live in libtarget and the later in lib/codegen/selectiondag?</div><div><br></div><div>Right now we have some clients (like LSR) that use TLI - but only inline methods and virtual methods - to avoid cyclic dependencies. This is gross :)</div><div><br></div><div>-Chris</div></body></html>