From 9dcb4b8744abb56cf9f3869efb413754002b1f97 Mon Sep 17 00:00:00 2001
From: sheepwall <a.sve@live.se>
Date: Fri, 8 Mar 2019 19:48:57 +0100
Subject: [PATCH] ..
---
examples/bare4.rs | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/examples/bare4.rs b/examples/bare4.rs
index 9af31a0..a585031 100644
--- a/examples/bare4.rs
+++ b/examples/bare4.rs
@@ -121,7 +121,8 @@ fn main() -> ! {
//
// Why is it important that ordering of volatile operations are ensured by the compiler?
//
-// ** your answer here **
+// ** If read/write instructions are reordered, the consequences are undefined, since peripherals
+// depend on the contents of registers that are read from/written to. **
//
// Give an example in the above code, where reordering might make things go horribly wrong
// (hint, accessing a peripheral not being powered...)
--
GitLab