5 Commits

Author	SHA1	Message	Date
Denis Vnukov	68b756bf90	Fix for rdar://19548610, Fuzzing Swift: performSema(...) crashes: Assertion failed: (Done && "Parser returned early?") ... Parser may stop at some erroneous constructions like stray #else or #endif, in some cases closing brace ‘}’, etc… continue parsing until we are done. Swift SVN r24822	2015-01-29 21:51:06 +00:00
Dmitri Hrybenko	6cad796ec8	Annotate compiler crasher tests so that the tests succeed reliably when ... the compiler is built without assertions Swift SVN r24061	2014-12-20 09:42:59 +00:00
Dmitri Hrybenko	1eea220932	Use one module cache directory for all the lit tests to speed them up ... Doing so is safe even though we have mock SDK. The include paths for modules with the same name in the real and mock SDKs are different, and the module files will be distinct (because they will have a different hash). This reduces test runtime on OS X by 30% and brings it under a minute on a 16-core machine. This also uncovered some problems with some tests -- even when run for iOS configurations, some tests would still run with macosx triple. I fixed the tests where I noticed this issue. rdar://problem/19125022 Swift SVN r23683	2014-12-04 11:21:48 +00:00
Chris Willmore	513b05c283	compiler_crashers: Use %target-swift-frontend instead of %swift -sdk %sdk ... This fixes compiler_crashers tests that use the ObjC interface on iOS hardware SDKs. Swift SVN r23458	2014-11-20 00:32:59 +00:00
Chris Willmore	4e1fa4a63f	Import the swift-compiler-crashes test suite. ... Add all compiler crash tests to the validation-test/compiler_crashers subdirectory. Add a RUN: line to each test case according to the current behavior of the Swift compiler. Swift SVN r23418	2014-11-19 01:27:58 +00:00