CPU Clock Cycle / IPC Performance Calculator implementation

Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

Record owner

Guth Instruments

Lifecycle

verified-clean

Evidence ID

t4-299

Effect

Computation or source lookup only

Input and validation requirements

CPI=0 produces an undefined IPS result and should be rejected; the input-schema CPI-versus-IPC switch and clock-rate unit convention can also produce drastically different outputs if interpreted incorrectly.

Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

{
  "inputs": {
    "clock_rate_hz": 2500000000,
    "instruction_count": 4000000000,
    "CPI": 1.25
  },
  "expected_outputs": {
    "execution_time_seconds": 2,
    "IPS": 2000000000,
    "MIPS": 2000
  },
  "working": "cycles = 4000000000 instructions × 1.25 cycles/instruction = 5000000000 cycles; execution time = 5000000000 cycles ÷ 2500000000 cycles/second = 2 seconds; IPS = 2500000000 cycles/second ÷ 1.25 cycles/instruction = 2000000000 instructions/second; MIPS = 2000000000 ÷ 1000000 = 2000 MIPS."
}

Other records

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

• VERIFIED_LEDGER.json
• evidence-tranche4/tranche4-results.json