Upload README.md with huggingface_hub

README.md

@@ -1,52 +1,17 @@
 ---
 language:
-- en
+  - en
 license: mit
 task_categories:
-- text-generation
+  - text-generation
 tags:
-- assembly
-- security
-- constant-time
-- side-channels
-- binsec
+  - assembly
+  - security
+  - constant-time
+  - side-channels
+  - binsec
 size_categories:
-- n<1K
-configs:
-- config_name: default
-  data_files:
-  - split: test
-    path: data/test-*
-dataset_info:
-  features:
-  - name: task_name
-    dtype: string
-  - name: flag_x86_64
-    dtype: string
-  - name: flag_aarch64_linux
-    dtype: string
-  - name: flag_riscv
-    dtype: string
-  - name: x86_64
-    dtype: string
-  - name: aarch64_linux
-    dtype: string
-  - name: riscv
-    dtype: string
-  - name: test_c
-    dtype: string
-  - name: binsec_output_x86_64
-    dtype: string
-  - name: binsec_output_aarch64_linux
-    dtype: string
-  - name: binsec_output_riscv
-    dtype: string
-  splits:
-  - name: test
-    num_bytes: 802772
-    num_examples: 10
-  download_size: 140894
-  dataset_size: 802772
+  - n<1K
 ---
 
 # RelBench-O2: Constant-Time Assembly at -O2
@@ -74,6 +39,9 @@ and **classification/repair** (decide whether a build leaks, and fix it if it do
 | `aarch64_linux` | AArch64 assembly at -O2 |
 | `riscv` | RISC-V RV64 (`rv64gc`/`lp64d`) assembly at -O2 |
 | `test_c` | C source of the BinSec harness (`test.c`) -- tags inputs secret/public through the `high_input_N` / `low_input_N` markers and calls the function under analysis |
+| `binsec_output_x86_64` | Full `binsec -checkct` log for the x86-64 `-O2` build -- the evidence `flag_x86_64` was parsed from, including the leaking instruction addresses |
+| `binsec_output_aarch64_linux` | Same, for the AArch64 `-O2` build |
+| `binsec_output_riscv` | Same, for the RISC-V `-O2` build |
 
 ## Statistics
 
@@ -103,7 +71,9 @@ markers with `nondet` (public), so BinSec knows which bytes are secret. It then
 **The verdict is per build.** The same program can be secure on one target and insecure on
 another, because the three backends make different branch/`cmov`/`csel` choices at -O2.
 That is why the verdict is not collapsed into one label: each target carries its own
-`flag_*` column.
+`flag_*` column, with the full analysis log in the matching `binsec_output_*` column --
+that log names the control-flow and memory-access checks that failed and at which
+addresses, so an `insecure` verdict can be traced back to a specific instruction.
 
 ## Usage
 
@@ -117,6 +87,7 @@ src_asm = record["x86_64"]  # source-side assembly
 tgt_asm = record["riscv"]   # reference target-side assembly
 leaky   = record["flag_riscv"] == "insecure"   # per-target verdict
 harness = record["test_c"]  # rebuild + recheck a candidate against BinSec
+why     = record["binsec_output_riscv"]  # the BinSec log behind flag_riscv
 ```
 
 ## Citation