Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove sole reference to embedded exponent #38

Merged
merged 1 commit into from
Jan 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
Loading