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
Kuba Mracek	a8312b6c1f	Mark tests that use the _Volatile module as REQUIRES: volatile	2024-06-19 10:13:14 -07:00
Kuba Mracek	1c66aeaa22	[Volatile] Mark VolatileMappedRegister as @frozen, transparent init, allow NULL pointer	2024-04-05 15:13:36 -07:00
Kuba Mracek	7d44c2be48	[Volatile] Add a -enable-experimental-feature Volatile	2024-04-05 15:13:30 -07:00
Kuba Mracek	e722fc70d7	[Volatile] Rename UnsafeVolatilePointer to VolatileMappedRegister, use 'unsafe' name in initializer	2024-04-05 15:13:03 -07:00
Kuba Mracek	90c8a8e90e	Add experimental _Volatile module providing low-level primitives for MMIO	2024-04-05 15:13:03 -07:00