From 7c5524276c20e0fc5c9e21f24b25e0a3b97b02ae Mon Sep 17 00:00:00 2001
From: anttib-5 <anttib-5@student.ltu.se>
Date: Fri, 8 Mar 2019 15:08:21 +0100
Subject: [PATCH] bare4_3
---
examples/bare4.rs | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/examples/bare4.rs b/examples/bare4.rs
index eee44e0..3c6e63b 100644
--- a/examples/bare4.rs
+++ b/examples/bare4.rs
@@ -127,16 +127,16 @@ fn main() -> ! {
//
// Why is it important that ordering of volatile operations are ensured by the compiler?
//
-// ** your answer here **
+// Since some operations has to be executed before others.
//
// 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 we swap row 59-60 with 63-64, then we wont get the nice blinking anymore.
//
// Without the non-reording proprety of `write_volatile/read_volatile` could that happen in theory
// (argue from the point of data dependencies).
//
-// ** your answer here **
+// Writing/Reading in wrong order may end up in unexpexed results
//
// Commit your answers (bare4_3)
--
GitLab