Bitfield Overlap Mask
Intersect exact nonnegative integer bit masks and retain the overlapping mask as decimal text.
Description
Intersect exact nonnegative integer bit masks and retain the overlapping mask as decimal text.
Two nonnegative integer masks overlap on the bits set in both. The overlap mask retains that evidence.
When to use this tool
Intersect exact nonnegative integer bit masks and retain the overlapping mask as decimal text.
- Prepare the supplied maskA, maskB fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter maskA, maskB. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.overlapMask, result.overlaps. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse maskA and maskB as exact nonnegative integer strings. Compute bitwise AND, return overlapMask as decimal text and overlaps when nonzero.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| maskA | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| maskB | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.overlapMask | The overlap mask value under the stated formula or text convention. |
| result.overlaps | Flag for overlaps under the exact condition described above. |
{
"input": {
"maskA": "12",
"maskB": "10"
},
"output": {
"result": {
"overlapMask": "8",
"overlaps": true
}
}
}Limitations and assumptions
- No fixed word width, signed representation or byte order is imposed.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Retain the field-width, bit-index and byte-order conventions when combining operations. Slicing, escaping, permutation and alignment are separate transforms; none supplies a complete framing or cryptographic protocol.
References
Similar or alternative tools
- Bitfield Mask Integer String
Build an exact arbitrary-width bitfield mask as a decimal integer string; zero width has a zero mask.
- Bitfield Gap Inventory
Inventory unoccupied bit positions and positive-width field overlaps in a bounded register; half-open spans.