From 543311a72ae124c719857a4b49d23e80da33e48d Mon Sep 17 00:00:00 2001 From: Dan Rollo Date: Thu, 26 Jan 2017 18:00:20 -0500 Subject: [PATCH] typo: harware to hardware --- GoArm.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GoArm.md b/GoArm.md index 651124da..9d8e98cd 100644 --- a/GoArm.md +++ b/GoArm.md @@ -63,7 +63,7 @@ willing to use, please refer to ` taskset(1) ` manual for details. # Known issues ## Lack of floating point hardware on ARMv5 -The major issue with ARMv5 is the lack of floating point support in common ARMv5 harware†. When compiled with the GOARM=5 environment variable, the 5l linker will insert a call to ` _sfloat ` before any block of floating point instructions to branch into the floating point emulator. This means that binaries produced with a Go installation that was compiled with soft float support will work on all supported architectures, but builds compiled without soft floating point support will not work on ARMv5. +The major issue with ARMv5 is the lack of floating point support in common ARMv5 hardware†. When compiled with the GOARM=5 environment variable, the 5l linker will insert a call to ` _sfloat ` before any block of floating point instructions to branch into the floating point emulator. This means that binaries produced with a Go installation that was compiled with soft float support will work on all supported architectures, but builds compiled without soft floating point support will not work on ARMv5. † This isn't strictly true, there exist ARMv5 implementations which have VFP1 floating point. However the compiler doesn't support VFP1 yet.