IEEE Binary64 Normal Exponent

Description

Decode unbiased exponent only for an IEEE binary64 normal raw pattern; other classes have null normal exponent, not an inferred finite value.

Binary floating-point storage separates sign, biased exponent and fraction fields. Zero and subnormal patterns use a different significand rule from normal values, and reserved exponent patterns represent infinity or NaN. These tools accept exact unsigned raw patterns as decimal integer text, preserving signed-zero and payload evidence without converting the bits into a JavaScript numeric value.

Decode unbiased exponent only for an IEEE binary64 normal raw pattern; other classes have null normal exponent, not an inferred finite value.

When to use this tool

Use this tool to decode unbiased exponent only for an IEEE binary64 normal raw pattern; other classes have null normal exponent, not an inferred finite value.

How to use the tool and how it works

Enter pattern using the input definitions below.
Run the operation. Resolve malformed-input errors before interpreting the result.
Read result.classification, result.exponent. Interpret signs, units, ordering and null values using the rules below.

Read an exact unsigned 64-bit pattern from decimal text. Its fields are one sign bit, 11 exponent bits and 52 fraction bits, with exponent bias 1023. Classify the pattern and subtract 1023 from the stored exponent only for normal patterns. Return exponent = null for zero, subnormal, infinity and NaN.^{[1, 2]}

Input field	Meaning and units	Accepted input
pattern	Exact unsigned 64-bit raw pattern as decimal integer text, from 0 through 2^64−1.	Text, at most 8,192 UTF-16 code units; the stated grammar and narrower limits also apply.

Output field	Interpretation
result	Object containing the fields below.
result.classification	Raw-bit class: zero, subnormal, normal, infinity or nan.
result.exponent	Unbiased exponent for a normal pattern, or null for every other raw-bit class.

json

{
  "input": {
    "pattern": "4607182418800017408"
  },
  "output": {
    "result": {
      "classification": "normal",
      "exponent": 0
    }
  }
}

Limitations and assumptions

A null normal exponent does not mean the pattern is invalid or has no finite value; subnormals use a different significand convention.
Pattern width is fixed by the tool name. Supply 0≤pattern<2^width as exact decimal integer text, not hexadecimal text or the represented float’s decimal value. Raw-bit operations preserve payloads without guaranteeing runtime NaN behavior.
Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.

Alternative or Complementary methods

Distinguish a raw unsigned bit pattern from the decimal value that pattern represents. Use field join/split operations for exact bit editing and a separate numeric conversion when a runtime floating-point value is required.

References

Numerical Computation Guide: IEEE Arithmetic — Oracle
Tool behavior and example: IEEE Binary64 Normal Exponent — tool.io

Similar or alternative tools

IEEE Binary16 Normal Exponent
Decode unbiased exponent only for an IEEE binary16 normal raw pattern; other classes have null normal exponent, not an inferred finite value.
IEEE Binary32 Normal Exponent
Decode unbiased exponent only for an IEEE binary32 normal raw pattern; other classes have null normal exponent, not an inferred finite value.