Erik Eckstein
1224cfa61b
update and unify the "please file a bug report" message
...
The new message is:
"Please submit a bug report (https://swift.org/contributing/#reporting-bugs ) and include the crash backtrace."
1. In crash logs we used to print a message which points to the llvm bug tracking page. Now it points to the swift.org bug tracking guidelines.
2. Use the same message in all compiler diagnostics which ask the user to file a bug report.
rdar://problem/70488534
2020-10-23 11:57:22 +02:00
Alexis Laferrière
2fbc063b2e
[Serialization] Note the misc version field of modules on deser. failures
...
This added information will hopefully help us understand hard to
reproduce deserialization failures.
2020-04-16 13:50:11 -07:00
John McCall
6ffeb4d839
[NFC] Add PrettyStackTraceConformance and use it
...
Also allow the printFooDescription functions to suppress
the trailing newline.
2018-11-15 18:39:35 -05:00
Jordan Rose
89db036429
[test] Update Serialization tests for Swift 3 removal
...
For the most part, this moves 3/4 tests to 4/5 tests.
2018-07-12 15:44:10 -07:00
Ted Kremenek
3da51018b6
Teach ClangImporter to handle effective Swift version with minor release.
...
Needed to support Swift 4.2.
2018-03-23 00:30:44 -07:00
Jordan Rose
a16d8a73d1
Bump the compiler version to 4.2 (and 3.4) ( #13767 )
...
https://swift.org/blog/4-2-release-process/
2018-03-02 18:09:45 -08:00
Ewa Matejska
1272cd3aac
Making master call itself 4.1, updating the swift 3 compatiblity mode to be 3.3 (from 3.2), adding ability to pass swift-version 5. Importer work not done yet.
2017-08-17 20:57:01 -07:00
Robert Widmann
71bf312a25
Migrate the rest of the tests to %empty-directory
2017-06-04 11:08:39 -07:00
Jordan Rose
e0c248c932
Turn on deserialization recovery by default. ( #9486 )
...
I'm still leaving a -disable-deserialization-recovery flag in there
just in case.
2017-05-11 08:47:59 -07:00
Ted Kremenek
4aa0f46fbb
Underlying Swift 3 version is now ‘3.2’
2017-04-22 22:15:44 -07:00
Jordan Rose
a2e0e27624
[test] Add some more tests for 73d4526.
...
There's still nothing really complicated going on here, such as an
override that previously satisfied a protocol conformance.
2017-04-10 16:38:59 -07:00
Jordan Rose
7e8d642e8e
[Serialization] When crashing, note if mix-and-match may be to blame.
...
That is, a Swift 3 target imported into a Swift 4 context or vice
versa. This requires serializing the compatibility mode explicitly,
instead of including it in the textual version string that's only
for debugging.
2017-04-10 16:38:58 -07:00
