=== THIS FUNCTION'S OWN HEADER (func_800D2A24, line 567) — read it in full ===
/* TU (src/md_MAIN_003/md_MAIN_003.c:1085) forward-declares this K&R-style as
 * `extern void func_800D2A24();` for its sole caller (func_800D2454, which
 * discards the return), so the definition here must be `void` to avoid
 * `conflicting types for 'func_800D2A24'` (cc1 exit 33). The body genuinely
 * sets $v0 to 1 or 0 on every exit path (asm: `addiu $v0,zero,1` /
 * `addu $v0,zero,zero`), and a plain `return <value>;` in a void function is
 * a pedwarn gcc-2.7.2 silently DISCARDS (loses those materializations,
 * closeness != 0 -- cookbook §43's void-return-value-drop). Absorbed at the
 * use site instead: a hard-`$2` register local set via a read-only
 * input-`__asm__` immediately before a bare `return;` on each exit forces
 * the same `li $v0,K` the s32-typed body would have emitted, without
 * widening the TU's declared return type. Putting the early-exit's v0-set
 * behind a `goto` (rather than inline in the `if` body) keeps that branch a
 * single instruction, matching the target's branch polarity -- inlining the
 * register-pin + asm barrier directly in the `if` block bloats it and flips
 * beqz/bnez (byte-verified: NEAR closeness 10 vs this MATCH closeness 0).
 */

