4 Commits

Author	SHA1	Message	Date
Slava Pestov	32316559f8	AST: Stored property accessors on non-Objective-C derived classes can be transparent ... In 74d979f0ac, the policy was changed so that only value type accessors are ever marked transparent, and not class accessors. This was intended to fix a bug where inlining an accessor of an Objective-C-derived class across module boundaries caused a linker failure because the accessor referenced a field offset variable, which has hidden visibility. However, this also caused a performance regression for Swift native classes. Bring back the old behavior for Swift native classes in non-resilient modules. Fixes <rdar://problem/29884727>.	2017-02-14 22:35:27 -08:00
Erik Eckstein	1d3724666f	tests: convert about 400 tests to the new mangling by using the -new-mangling-for-tests option ... When the new mangling is enabled permanently, the option can be removed from the RUN command lines again.	2017-01-24 15:27:45 -08:00
Erik Eckstein	74d979f0ac	SILGen: Don’t make class accessors transparent. ... Because when they are inlined they might access hidden symbols in another module, like the field offset variable. fixes rdar://problem/29707641	2016-12-19 17:02:09 -08:00
Michael Gottesman	0bfda96ace	[sil-func-extractor] Teach sil-extract to extract a list of functions and the inverse of a list of functions. Also rename to sil-func-extractor to make it clearer what it is doing. ... This will allow for modules to be split from the command line using a script. The one thing that is missing from this still is that it does not handle shared functions in IMO a satisfactory way. Given that we are splitting a module, my feeling that the correct way to do this is to create a public shim for the shared function in the module that the shared function gets put in and let all other users use that entry point. But I need to think about this a bit more.	2016-12-08 18:29:33 -08:00