5 Commits

Author	SHA1	Message	Date
Arnold Schwaighofer	4d94eff93c	Respect runtime-compatibility-version flag also for dynamic replacement compatibility library ... rdar://56259688	2019-10-15 10:31:18 -07:00
Arnold Schwaighofer	5d329464d6	Use thread private key to avoid weak linkage ... We use one bit of the third reserved swift private tls key. Also move the functionality into a separate static archive that is always linked dependent on deployment target.	2019-06-17 15:03:45 -07:00
Joe Groff	4ed8de10f9	Revert "Revert "Use autolinking to pull in compatibility libraries.""	2019-06-03 20:10:51 -07:00
Joe Groff	a7cc3a38cc	Revert "Use autolinking to pull in compatibility libraries."	2019-06-03 14:18:39 -07:00
Joe Groff	dffd1b27a1	Use autolinking to pull in compatibility libraries. ... Many build systems that support Swift don't use swiftc to drive the linker. To make things easier for these build systems, also use autolinking to pull in the needed compatibility libraries. This is less ideal than letting the driver add it at link time, since individual compile jobs don't know whether they're building an executable or not. Introduce a `-disable-autolink-runtime-compatibility` flag, which build systems that do drive the linker with swiftc can pass to avoid autolinking. rdar://problem/50057445	2019-05-31 13:11:14 -07:00