6 Commits

Author	SHA1	Message	Date
Kuba Mracek	d8c0c25b4b	[embedded] Centralize the OS/target requirements on (most) Embedded Swift tests	2025-01-19 11:44:55 -08:00
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
Joe Groff	51829c17bf	@_extern is an experimental feature. ... Mark it as such. rdar://132013078	2024-07-18 11:46:16 -07:00
Kuba Mracek	a8312b6c1f	Mark tests that use the _Volatile module as REQUIRES: volatile	2024-06-19 10:13:14 -07:00
Yuta Saito	65723193a9	[embedded] Use @_extern(c) instead of @_silgen_name for putchar in tests ... Using inconsistent attributes between stdlib and tests causes compilation errors. There are still several misuses of @_silgen_name in tests, but leaving them as is for now to incrementally fix them.	2024-04-11 10:37:25 +00:00
Kuba Mracek	4b7c678bb7	[Volatile] Add executable tests for VolatileMappedRegister	2024-04-05 15:31:02 -07:00