<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jul 27, 2012, at 7:05 PM, Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jul 27, 2012, at 1:39 PM, Tom Stellard wrote:</div><blockquote type="cite"><font class="Apple-style-span"><br></font><blockquote type="cite">We also need to come up with a plan regarding cutting releases. When<br></blockquote><blockquote type="cite">3.2 is branched, will all "staged" back-ends be removed? Or will<br></blockquote><blockquote type="cite">they be left in the distribution so interested parties can build<br></blockquote><blockquote type="cite">them?<br></blockquote><blockquote type="cite"><br></blockquote><br>I can't really think of any disadvantages to keeping staged backends<br>in releases. Being in a release would help a backend get more exposure<br>and increase the number of users/testers it would get.<br></blockquote><div><br></div><div>I agree, there is no reason to remove it from the source drop of the release. The binaries produced for each release shouldn't include them though.</div></div></div></blockquote><div><br></div><div>Sounds good to me, I agree that more exposure is best.</div><div><br></div><div>In terms of build system integration, I think it makes sense to do the following:</div><div><br></div><div><ol class="MailOutline"><li>Add a ENABLE_EXPERIMENTAL or ENABLE_STAGING flag that allows experimental features to be built (default: OFF)</li><li>Add an LLVM_STAGING_TARGETS list that contains all of the staging back-ends</li><li>Allow LLVM_TARGETS_TO_BUILD to contain a back-end from LLVM_STAGING_TARGETS *only* if ENABLE_STAGING is ON</li></ol><div><br></div><div>This will allow the default configuration to not only skip the staging back-ends, but prohibit them from being built without explicitly setting ENABLE_STAGING. Further, this will allow picking-and-choosing which staging back-ends to build.</div><div><br></div><div>Is there any reason not to try this out with the R600 target?</div></div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>-Chris</div><br></div></blockquote></div><br></body></html>