Skip to content

[FreeBSD] Add unsafe labels for strict memory safety #82845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions stdlib/public/Synchronization/Mutex/FreeBSDImpl.swift
Original file line number Diff line number Diff line change
Expand Up @@ -30,20 +30,20 @@ public struct _MutexHandle: ~Copyable {
@_alwaysEmitIntoClient
@_transparent
internal borrowing func _lock() {
_umtx_op(value._address, UMTX_OP_MUTEX_LOCK, 0, nil, nil)
unsafe _umtx_op(unsafe value._address, UMTX_OP_MUTEX_LOCK, 0, nil, nil)
}

@available(SwiftStdlib 6.0, *)
@_alwaysEmitIntoClient
@_transparent
internal borrowing func _tryLock() -> Bool {
_umtx_op(value._address, UMTX_OP_MUTEX_TRYLOCK, 0, nil, nil) != -1
unsafe _umtx_op(unsafe value._address, UMTX_OP_MUTEX_TRYLOCK, 0, nil, nil) != -1
}

@available(SwiftStdlib 6.0, *)
@_alwaysEmitIntoClient
@_transparent
internal borrowing func _unlock() {
_umtx_op(value._address, UMTX_OP_MUTEX_UNLOCK, 0, nil, nil)
unsafe _umtx_op(unsafe value._address, UMTX_OP_MUTEX_UNLOCK, 0, nil, nil)
}
}