Skip to content

Commit

Permalink
Remove & fix references to embedded exponent
Browse files Browse the repository at this point in the history
"Embedded" and "internal" have very similar meanings in English so it's pretty confusing for them to mean opposite things in CHERI. Fortunately there were only two references to "embedded" so it's easy enough to remove it.
  • Loading branch information
Timmmm committed Jan 25, 2024
1 parent 85790d4 commit a18c7ee
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/cap-description.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -225,7 +225,7 @@ address
into the capability's address
* *EF:* Exponent format flag indicating the encoding for T, B and E
** The exponent is stored in T and B if EF=0, so it is 'internal'
** The exponent is zero if EF=1, so it is 'embedded'
** The exponent is zero if EF=1

The bit width of T and B are defined in terms of the mantissa width (MW) which
is set depending on the value of XLENMAX as shown in
Expand Down Expand Up @@ -505,7 +505,7 @@ bounds are formed of two or three sections:
* Upper bits from the address
* Middle bits from T and B decoded from the metadata
* Lower bits are set to zero
** This is only if there is an embedded exponent (EF=0)
** This is only if there is an internal exponent (EF=0)

.Composition of address bounds
[#comp_addr_bounds,options=header,align="center"]
Expand Down

0 comments on commit a18c7ee

Please sign in to comment.