Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit be789e6

Browse files
committedMay 30, 2025·
llvm-assumptions: reference LLVM issue
1 parent f499068 commit be789e6

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed
 

‎resources/llvm-assumptions.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ Let's collect a list of those cases here.
88
Alive says that this yields poison.
99
- To implement the desired semantics for `MaybeUninit<$int>` we need a type of arbitrary size that can hold arbitrary data -- including provenance.
1010
LLVM currently has no such type, the only type that is fully guaranteed to support provenance is `ptr` and that has a fixed size.
11+
[LLVM issue](https://github.com/llvm/llvm-project/issues/142141)
1112
- This one is not about current Rust but about possible future extensions:
1213
when LLVM returns `poison` for some operation, we can *not* say that this corresponds to `uninit` in Rust. We *must* declare this immediate UB.
1314
The reason for this is that LLVM does not really support `poison` being stored in memory; Rust's `uninit` can therefore only correspond to LLVM's `undef`.

0 commit comments

Comments
 (0)
Please sign in to comment.