about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2022-10-27 09:25:09 +0200
committerGitHub <noreply@github.com>2022-10-27 09:25:09 +0200
commit0cd87148d905e4b7dd0599edcd2866dd3ea7ffb7 (patch)
tree790bba25492d96d7d60a9369d43c1dbc6748733a /compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp
parent2937621aa7ad494b1ef2da3a8e814ac6e101e181 (diff)
parentbd947632b5da12ccb28a446a62898862f8f415ed (diff)
downloadrust-0cd87148d905e4b7dd0599edcd2866dd3ea7ffb7.tar.gz
rust-0cd87148d905e4b7dd0599edcd2866dd3ea7ffb7.zip
Rollup merge of #103106 - saethlin:from_exposed_docs, r=thomcc
Try to say that memory outside the AM is always exposed

cc ``@Gankra`` ``@thomcc``

I want to confidently tell people that they can use `from_exposed_addr` to get a pointer for doing MMIO and/or other hardware interactions done with volatile reads/writes at particular addresses outside the Rust AM. Currently, the docs indicate that would be UB.

With this change, now the docs indicate that this is intended to be a valid use of `from_exposed_addr`.

r? ``@RalfJung``
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions