<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;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 7, 2016, at 14:01, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Apr 6, 2016, at 11:08 AM, Jordan Rose via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:<br class=""><br class="">I imagine it's because your git hash has changed, which is used in the --version output for swiftc. I'm not sure how to avoid that cost entirely, but we could add a CMake option to not do it (which you could set locally), and we could probably move it to a library that isn't used by most of those tools (so that we're only re-linking swiftc).<br class=""></blockquote><br class="">Could we move the hash to be a text file stored next to the executables in the installdir? That way the text file gets updated, but not the binaries?</div></div></blockquote><br class=""></div><div>Oh, that's clever. Maybe that's good enough for local builds. I'd want to be careful about it for the binary we ship (to not waste an fstat).</div><div><br class=""></div><div>FWIW this isn't <i class="">quite</i> just --version output; we also stamp it into swiftmodule files. But any build with an actual submission tag will use that instead.</div><div><br class=""></div><div>Jordan</div><br class=""></body></html>