Files
swift-mirror/test/Volatile/volatile-exec.swift
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

33 lines
1.0 KiB
Swift

// RUN: %target-run-simple-swift(-parse-as-library -enable-experimental-feature Volatile) | %FileCheck %s
// REQUIRES: executable_test
// REQUIRES: volatile
// REQUIRES: swift_feature_Volatile
import _Volatile
@main
struct Main {
static func main() {
var byte: UInt8 = 42
withUnsafePointer(to: &byte) { p in
let volatilePointer = VolatileMappedRegister<UInt8>(unsafeBitPattern: UInt(bitPattern: p))
print("byte = \(volatilePointer.load())")
// CHECK: byte = 42
volatilePointer.store(77)
}
print("byte = \(byte)")
// CHECK: byte = 77
var heapPointer = UnsafeMutablePointer<UInt8>.allocate(capacity: 16) // uninitialized content
for i in 0 ..< 16 {
let pointerWithOffset = heapPointer.advanced(by: i)
let volatilePointer = VolatileMappedRegister<UInt8>(unsafeBitPattern: UInt(bitPattern: pointerWithOffset))
volatilePointer.store(UInt8(0x61 + i))
}
heapPointer[15] = 0
print(String(cString: heapPointer))
// CHECK: abcdefghijklmno
}
}