5 Commits

Author	SHA1	Message	Date
Erik Eckstein	c4a11f4c92	tests: remove the now unused option -new-mangling-for-tests	2017-03-22 11:28:43 -07:00
Roman Levenstein	4b965b6093	Un-XFAIL some tests which are passing now, after merging PR #7350	2017-03-17 07:24:46 -07: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
Slava Pestov	d28b8ead50	Add resilient_stdlib to available_features and XFAIL remaining failing tests ... All unoptimized tests should now pass when Swift is built with 'build-script -- --swift-stdlib-enable-resilience=1'. There are still some issues when the tests themselves are built with optimizations via 'check-swift-validation-optimize'. Fixes <rdar://problem/28409189>.	2016-09-30 18:28:12 -07:00
Andrew Trick	aacee48cca	Fix UnsafeRawPointer.load to use Builtin.loadRaw. ... This API should have been converted to use the new Builtin before it was introduced here: commit a41484ea2b Author: Andrew Trick <atrick@apple.com> Date: Fri Jul 22 13:32:08 2016 Add UnsafeRawPointer type and API. (#3677) But it looks like that was dropped during during some local merge. It's not likely to be a problem until developers start adopting the new API and the optimizer starts using TBAA aggressively. The other "raw" API's are binding memory or using memmove, so those are safe. rdar:23406272.	2016-08-13 18:49:32 -07:00