From a7528994316b942895b00cc3ccf64af2d47a8e30 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Sat, 15 Jul 2017 17:50:46 -0700 Subject: [PATCH 1/1] typo --- ralf/_posts/2017-07-14-undefined-behavior.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ralf/_posts/2017-07-14-undefined-behavior.md b/ralf/_posts/2017-07-14-undefined-behavior.md index 732117a..1da732e 100644 --- a/ralf/_posts/2017-07-14-undefined-behavior.md +++ b/ralf/_posts/2017-07-14-undefined-behavior.md @@ -39,7 +39,7 @@ This could be the end of the game: No alias information, no way to verify our a ## Shifting responsibility -However, it turns out that compilers writers consider these optimizations important enough that they came up with an alternative solution: +However, it turns out that compiler writers consider these optimizations important enough that they came up with an alternative solution: Instead of having the compiler verify such assumptions, they declared the programmer responsible. For example, the C standard says that memory accesses have to happen with the right "effective type": If data was stored with a `float` pointer, it must not be read with an `int` pointer. -- 2.30.2