From 2e02a7c592735da26d65b909cf82a10019348a8b Mon Sep 17 00:00:00 2001 From: Carolyn Zech Date: Fri, 13 Sep 2024 18:31:33 -0400 Subject: [PATCH] remove intrinsics paragraph --- doc/src/challenges/0007-atomic-types.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/src/challenges/0007-atomic-types.md b/doc/src/challenges/0007-atomic-types.md index e80fda53d657a..5581809f68516 100644 --- a/doc/src/challenges/0007-atomic-types.md +++ b/doc/src/challenges/0007-atomic-types.md @@ -82,11 +82,6 @@ Then, write and verify safety contracts for the remaining unsafe functions: - `atomic_umax` - `atomic_umin` -These functions are wrappers around compiler intrinsics. -Thus, your task is to ensure that we cannot cause undefined behavior by invoking the intrinsics on these inputs. -For instance, if the intrinsic takes as input a raw pointer and reads the value at that pointer, your contracts should ensure that we would not cause UB by performing the read. -For the purpose of this challenge, you may assume that any UB in the intrinsics would be a direct consequence of malformed inputs. - You are not required to write correctness contracts for these functions (e.g., that `atomic_sub` correctly subtracts the operands and stores the result), but it would be great to do so! #### Part 2: Reentrant Lock