From 7ce9a1b46bff89757eba280b9dd8dd4ab900cbc4 Mon Sep 17 00:00:00 2001 From: Aaron Taylor Date: Sun, 10 Jan 2021 22:33:03 -0800 Subject: [PATCH] Minor changes to cross compiler howto. --- .../modern_c_software_development/pdp11-cross-compiler.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/data/development/pdp-11/modern_c_software_development/pdp11-cross-compiler.md b/data/development/pdp-11/modern_c_software_development/pdp11-cross-compiler.md index 965b242..7df9471 100644 --- a/data/development/pdp-11/modern_c_software_development/pdp11-cross-compiler.md +++ b/data/development/pdp-11/modern_c_software_development/pdp11-cross-compiler.md @@ -161,7 +161,7 @@ If we try to compile this code, we receive two errors from the linker. The two functions referenced, `__umodhi3` and `__udivhi3` are part of `libgcc`. The names reference the **u**nsigned **mod**ulo or **div**ision on -**h**alf-**i**teger types. Per the [GCC +**h**alf-**i**nteger types. Per the [GCC manual](https://gcc.gnu.org/onlinedocs/gccint/Machine-Modes.html#Machine-Modes), the half-integer mode uses a two-byte integer. @@ -180,7 +180,7 @@ The second option is to implement your own functions for `__umodhi3()`, functional, though catching all the edge cases could be challenging. -## uint32 ## +## Using uint32 ## Although the PDP-11 utilizes a 16-bit word, GCC is clever enough to allow operations on 32-bit words by breaking them up into smaller operations. For -- 2.20.1