6 Commits

Author	SHA1	Message	Date
Daniel Rodríguez Troitiño	ba68faaed5	[test] Mark tests that use experimental/upcoming features as such ... Find all the usages of `--enable-experimental-feature` or `--enable-upcoming-feature` in the tests and replace some of the `REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which should correctly apply to depending on the asserts/noasserts mode of the toolchain for each feature. Remove some comments that talked about enabling asserts since they don't apply anymore (but I might had miss some). All this was done with an automated script, so some formatting weirdness might happen, but I hope I fixed most of those. There might be some tests that were `REQUIRES: asserts` that might run in `noasserts` toolchains now. This will normally be because their feature went from experimental to upcoming/base and the tests were not updated.	2024-11-02 11:46:46 -07:00
Erik Eckstein	709dfc2d21	MandatoryPerformanceOptimization: don't let not-inlinable functions to be inlined ... Also refactor canInline. Fixes a compiler crash. rdar://137544788	2024-10-15 12:19:50 +02:00
Kuba Mracek	cf2437ae2b	[embedded] Avoid using removed print.swift in test/embedded/dictionary-runtime.swift	2024-01-16 13:40:41 -08:00
Kuba Mracek	e1be24fa2d	[embedded] Also test -Osize in embedded/dictionary-runtime.swift	2024-01-16 13:40:13 -08:00
Kuba Mracek	f5b7835998	[embedded] Adjust test/embedded/dictionary-runtime.swift to use print.swift	2024-01-16 13:40:13 -08:00
Kuba Mracek	392f2c36eb	[embedded] Add Dictionary to embedded stdlib	2024-01-16 13:40:13 -08:00