Is possible to “protect path to swift-backtrace” and “protect environment for swift-backtrace”? If yes, how? If not, can the “unable to protect” messages be disabled?

The scenario is a Swift Community Apt Repository installation of Swift on a Raspberry Pi 5 with Raspberry Pi OS. The command swift --version is sufficient to invoke the message:

swift --version
#swift runtime: unable to protect path to swift-backtrace at 0x7fff2ffa7000: 22; disabling backtracing.
#swift runtime: unable to protect environment for swift-backtrace at 0x7fff2ff9f000: 22; disabling backtracing.
#swift runtime: unable to protect path to swift-backtrace at 0x7fff8a907000: 22; disabling backtracing.
#swift runtime: unable to protect environment for swift-backtrace at 0x7fff8a8ff000: 22; disabling backtracing.
#swift runtime: unable to protect path to swift-backtrace at 0x7fffafe97000: 22; disabling backtracing.
#swift runtime: unable to protect environment for swift-backtrace at 0x7fffafe8f000: 22; disabling backtracing.
#Swift version 5.10 (swift-5.10-RELEASE)
#Target: aarch64-unknown-linux-gnu

In contrast, a Swift Community Apt Repository installation on Ubuntu does not have the “unable to protect” issue:

swift --version
#Swift version 5.10 (swift-5.10-RELEASE)
#Target: x86_64-unknown-linux-gnu