From ae61fba0fd956af2a41a0211a8a6ce367ebd7ffe Mon Sep 17 00:00:00 2001
From: Josef Utbult <josutb-7@student.ltu.se>
Date: Fri, 5 Mar 2021 15:24:06 +0100
Subject: [PATCH] bare4_3
---
examples/rtic_bare4.rs | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/examples/rtic_bare4.rs b/examples/rtic_bare4.rs
index 2637ed6..2c57c13 100644
--- a/examples/rtic_bare4.rs
+++ b/examples/rtic_bare4.rs
@@ -126,7 +126,8 @@ const APP: () = {
// Give an example in the above code, where reordering might make things go horribly wrong
// (hint, accessing a peripheral not being powered...)
//
-// ** your answer here **
+// If you have a register being accessed before its been setup correctly yet, there would
+// be undefined behaviour.
//
// Without the non-reordering property of `write_volatile/read_volatile` could that happen in theory
// (argue from the point of data dependencies).
--
GitLab