INSTALL DBYTE 12.4. VERIFY THE ZIP FIRST.

00 download

DOWNLOAD dbyte-v12.4.0-windows-x64.zip · READ PACKAGE MANIFEST

EXPECTED BYTES   3855311
EXPECTED FILES   450
EXPECTED SHA256  433B18BBFD5C36304558A71FE169E631757DBD5285AD16C9097B36E64EE1E55F

10 verify the bytes

$Zip = ".\dbyte-v12.4.0-windows-x64.zip"
$Expected = "433B18BBFD5C36304558A71FE169E631757DBD5285AD16C9097B36E64EE1E55F"
$Actual = (Get-FileHash -LiteralPath $Zip -Algorithm SHA256).Hash
if ($Actual -ne $Expected) { throw "DBYTE 12.4 PACKAGE HASH MISMATCH" }
if ((Get-Item -LiteralPath $Zip).Length -ne 3855311) { throw "DBYTE 12.4 PACKAGE SIZE MISMATCH" }

Do both checks. SHA-256 already covers the size indirectly, but the explicit byte count catches obvious wrong-file mistakes before you start arguing with a hash.

20 extract to a clean directory

Expand-Archive -LiteralPath .\dbyte-v12.4.0-windows-x64.zip -DestinationPath .\dbyte-12.4
Set-Location .\dbyte-12.4
.\dbyte.exe --version
.\dbytec.exe --version

EXPECTED RELEASE  12.4.0
SOURCE COMMIT      a1a5c2458065f6f295d1c3e77df62a34846226e3

If the extracted version does not say 12.4.0, stop there. A PATH collision or wrong directory is cheaper to fix before you start testing the compiler.

30 run something boring

.\dbyte.exe run examples\hello.dby
.\dbyte.exe run --vm examples\hello.dby

The first test should be boring. You are verifying installation and execution path, not showing off the type system. Once hosted and VM execution agree on a tiny program, move on.

Do not debug register allocation when the real bug is that PowerShell is running last month's executable.

40 compile native code

.\dbytec.exe build examples\hello.dby --target x86_64-dbyte-windows --emit exe --opt-level 1
.\dbytec.exe build examples\hello.dby --target x86_64-dbyte-windows --emit exe --opt-level 0

O1 is the production default. O0 exists for diagnosis and comparison. Both are required to preserve the same language and ownership behavior.

50 inspect when something looks wrong

Use the native inspection options, including --dump-native-mir, before guessing. Read MACHINE INSPECTION for the debugging order and O0 / O1 for optimization boundaries.

60 what to read next

INSTALL LAW. One known ZIP. One known hash. One known executable. Cut the problem until the machine can answer yes or no.