From 2d735388f5acb6a6c6e722929787faa44d82b2f2 Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Sun, 17 Jan 2021 22:50:31 +0000 Subject: [PATCH] spelling --- openpower/sv/overview.mdwn | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/openpower/sv/overview.mdwn b/openpower/sv/overview.mdwn index d24f5bec3..7d5d40c6c 100644 --- a/openpower/sv/overview.mdwn +++ b/openpower/sv/overview.mdwn @@ -509,12 +509,15 @@ clarity and assumes significant working knowledge of OpenPOWER, with arbitrary insertions of 7-index here and 3-bitindex there, the decision to pick LE was extremely easy. -Without such a decision, if two words are packed as elements into a -64 bit register, what does this mean? Should they be inverted so that -the lower indexed element goes into the HI or the LO word? should the -8 bytes of each register be inverted? Should the bytes in each element -be inverted? Should the element indexing loop order be broken onto discontiguous chunks such as 32107654 rather than 01234567, and if so at what granilsrity of discontinuity? These are all equally valid and legitimate interpretations -of what constitutes "BE" and they all cause merry mayhem. +Without such a decision, if two words are packed as elements into a 64 +bit register, what does this mean? Should they be inverted so that the +lower indexed element goes into the HI or the LO word? should the 8 +bytes of each register be inverted? Should the bytes in each element +be inverted? Should the element indexing loop order be broken onto +discontiguous chunks such as 32107654 rather than 01234567, and if so +at what granularity of discontinuity? These are all equally valid and +legitimate interpretations of what constitutes "BE" and they all cause +merry mayhem. The decision was therefore made: the c typedef union is the canonical definition, and its members are defined as being in LE order. From there, -- 2.30.2