Adversarial responseAlgorithms and systems performancereviewed 2026-07-16

Shorter and faster than Sort3AlphaDev

Certiv evidence level

Selected check replayed

central claim independently reproduced?

No.

That answer stays “no” even when a selected check passed.

claim boundary

Three statements that must not be collapsed.

01 · authors report

The author presents shorter Sort3 implementations and a C/C++ implementation claimed to be faster than the published AlphaDev version.

02 · Certiv observed

Eight supplied sorting functions passed 17,173,580 cases in an independent harness. On one i9-13900KF environment with Clang 14, a nine-trial microbenchmark measured Sort3_faster at a 0.837 ns/call median versus 1.031 ns/call for Sort3AlphaDev.

03 · not established

The run does not prove correctness over all machine states, universal instruction minimality, or generalized speed across CPUs, compilers, workloads, and measurement methods.

source identity

The paper is versioned bytes.

A mutable title or unversioned link is not enough to reproduce what was reviewed.

arXiv version
2307.14503v1
Submitted
2023-07-23
Version date
2023-07-23
Size
67,617 bytes · 5 pages
PDF SHA-256
7359b5844b5826bb269b3e552bd8f57b53c1c2854ba4aaea9c525fd4b6929b34

Observed parser properties

  • Recognized as a PDF and not encrypted.
  • pdfinfo reported JavaScript: no.
  • pdfdetach reported no embedded files.
  • pdftotext completed successfully.

These probes reduce ambiguity and obvious PDF attack surface. They are not a comprehensive malware analysis.

Certiv T0 exercise: this exact PDF was hash-pinned without executing its declared command. The unchanged input remained explicitly unverifiable; a one-byte tamper produced a failed input_hash_drift finding.

test record

Checks, failures, and blockers.

Status is always paired with text. A pass applies only to the check and boundary shown in the same row.

Observed

Exact PDF identity

Observed

The downloaded v1 PDF matched the recorded SHA-256, byte count, and page count.

Boundary

This establishes file identity only.

Passed · bounded

Author test under Clang

Observed

The repository's supplied test program compiled with Clang and returned success.

Boundary

Its 'exhaustive' label covers only 13 explicit cases, and its process exit status does not fail when an individual function reports failure.

Passed · bounded

Independent functional stress test

Observed

Eight functions passed 17,173,580 deterministic cases: signed domains for five functions, nonnegative domains for three documented variants, plus edge cases.

Boundary

This is broad finite-domain evidence, not a proof for every possible integer triple or target architecture.

Failed probe

GCC 11.4 portability probe

Observed

Direct compilation failed on the inline-assembly movsb destination syntax; Clang 14 compiled it.

Boundary

This is a portability finding, not a functional counterexample under the documented Clang-compatible path.

Passed · bounded

Bounded one-host timing comparison

Observed

Across nine 5,000,000-call trials: Sort3_faster median 0.837 ns/call (0.794–0.863); Sort3AlphaDev median 1.031 (0.983–1.131). Checksums matched.

Boundary

One virtualized host, compiler, optimization mode, and deterministic input stream cannot establish universal performance.

external artifacts

Pinned, not trusted by default.

Sort3 response repository

Observed revision431ac0efcc216792f10e8f23d24a8ee387b3c348

Recorded SHA-256b99439b6013fadde20b57fafe40643913a0bb0a2c48d93659865c7f81344fdee

SHA-256 is for sort.h. The independent harness SHA-256 is 4475c66c5030ccf3949d2bdb0aa51e2ab8115d94487d77049bfc66788a02d551; benchmark harness SHA-256 is 4b5464cc80a8f3684813b36403db97d9b9b6b3925fa56262a465eb85fa08edd3.

red-team findings

Where a confident summary can outrun the evidence.

  • The repository's test is not exhaustive despite its label and has weak failure propagation.
  • Sort3_15 is documented in the repository erratum as valid only for nonnegative inputs.
  • The inline assembly compiled under Clang 14 but failed under GCC 11.4, exposing a portability boundary.
  • Performance evidence must state CPU, compiler, input distribution, trial count, and measurement scope.

primary sources

Follow the evidence outward.

Dossier certiv-ai-discovery-2026-07-16/sort3-response. Certiv produced this test record; the paper authors did not issue or endorse it.