Skip to content

Main content

Bitwise: Bitfield Width From Endpoints Tool

Resolve an inclusive zero-based bitfield width inside an explicit word, rejecting inverted or out-of-word endpoints.

Loading tool…

Description

Return field width from inclusive bit endpoints.

Bit positions are usually counted from the least-significant bit, while a displayed binary string has its own left-to-right indexing convention. Masks, fields and parity predicates describe a selected region or pattern; local agreement does not validate a complete encoded record.

Return field width from inclusive bit endpoints.

When to use this tool

Use Bitwise: Bitfield Width From Endpoints when checking the stated mask, field, parity or bit-index convention.

How to use the tool and how it works

  1. Enter lowBit, highBit, wordWidth. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Return field width from inclusive bit endpoints. Require wordWidth 1..128 and 0 <= lowBit <= highBit < wordWidth; width = high-low+1.1

Input fieldMeaning and unitsAccepted input
lowBitLow BitRequired. Safe integer. Calculation range: 0 through wordWidth - 1, inclusive.
highBitHigh BitRequired. Safe integer. Calculation range: lowBit through wordWidth - 1, inclusive.
wordWidthWord WidthRequired. Safe integer. Calculation range: 1 through 128, inclusive.
Output fieldInterpretationReturned shape
resultReturned calculated value or nested object under the stated output convention.Required. Object.
result.widthWidth under the stated bit, interval or geometry convention; apply the field-specific units and bounds.Calculated result member: number.
json
{
  "input": {
    "lowBit": 2,
    "highBit": 5,
    "wordWidth": 8
  },
  "output": {
    "result": {
      "width": 4
    }
  }
}

Limitations and assumptions

  • This requires a nonempty field and uses least-significant-based endpoint labels without extracting or moving bits.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Choose an explicit bit order, word width and missing-position policy; use the complete record format and appropriate parsing or checksum methods for full validation.

References

  1. Calculation and input contract: bitwise/bitfield-width-from-endpoints — tool.io

Similar or alternative tools