From e49fc18b684c953e3d920dcfc4bfce8ede9268dd Mon Sep 17 00:00:00 2001 From: titzer Date: Tue, 11 Oct 2016 17:47:02 +0200 Subject: Structured stack (#813) * Rename AstSemantics.md to Semantics.md * Rewrite Semantics for structured stack machine * Update control instructions * Update nop * More tweaks * Update README.md * Update Semantics.md * Update Semantics.md * Address @rossberg-chromium comments --- CAndC++.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'CAndC++.md') diff --git a/CAndC++.md b/CAndC++.md index 236672c..76866e2 100644 --- a/CAndC++.md +++ b/CAndC++.md @@ -88,7 +88,7 @@ optimizers still assume that undefined behavior won't occur, so such bugs can still lead to surprising behavior. For example, while unaligned memory access is -[fully defined](AstSemantics.md#alignment) in WebAssembly, C and C++ compilers +[fully defined](Semantics.md#alignment) in WebAssembly, C and C++ compilers make no guarantee that a (non-packed) unaligned memory access at the source level is harmlessly translated into an unaligned memory access in WebAssembly. And in practice, popular C and C++ compilers do optimize on the assumption that @@ -116,7 +116,7 @@ rather than on the underlying platform. For those details that are dependent on the platform, on WebAssembly they follow naturally from having 8-bit bytes, 32-bit and 64-bit two's complement integers, and [32-bit and 64-bit IEEE-754-2008-style floating point support] -(AstSemantics.md#floating-point-operators). +(Semantics.md#floating-point-operators). ## Portability of compiled code -- cgit v1.2.3