mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

remove the memcpy-on-equal-ptrs assumption

Browse Source
This commit is contained in:
Ralf Jung 2023-11-24 21:23:45 +01:00
parent 42ae1a7615
commit 73042206dd
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
library/core/src/lib.rs
View File

@ -24,9 +24,8 @@
//! which are generated by Rust codegen backends. Additionally, this library can make explicit //! which are generated by Rust codegen backends. Additionally, this library can make explicit
//! calls to `strlen`. Their signatures are the same as found in C, but there are extra //! calls to `strlen`. Their signatures are the same as found in C, but there are extra
//! assumptions about their semantics: For `memcpy`, `memmove`, `memset`, `memcmp`, and `bcmp`, if //! assumptions about their semantics: For `memcpy`, `memmove`, `memset`, `memcmp`, and `bcmp`, if
//! the `n` parameter is 0, the function is assumed to not be UB. Furthermore, for `memcpy`, if //! the `n` parameter is 0, the function is assumed to not be UB, even if the pointers are NULL or
//! source and target pointer are equal, the function is assumed to not be UB. //! dangling. (Note that making extra assumptions about these functions is common among compilers:
//! (Note that these are standard assumptions among compilers:
//! [clang](https://reviews.llvm.org/D86993) and [GCC](https://gcc.gnu.org/onlinedocs/gcc/Standards.html#C-Language) do the same.) //! [clang](https://reviews.llvm.org/D86993) and [GCC](https://gcc.gnu.org/onlinedocs/gcc/Standards.html#C-Language) do the same.)
//! These functions are often provided by the system libc, but can also be provided by the //! These functions are often provided by the system libc, but can also be provided by the
//! [compiler-builtins crate](https://crates.io/crates/compiler_builtins). //! [compiler-builtins crate](https://crates.io/crates/compiler_builtins).