Upload README.md with huggingface_hub

README.md

@@ -1,46 +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
-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
-  splits:
-  - name: test
-    num_bytes: 765528
-    num_examples: 10
-  download_size: 119846
-  dataset_size: 765528
-configs:
-- config_name: default
-  data_files:
-  - split: test
-    path: data/test-*
+  - n<1K
 ---
 
 # RelBench-O2: Constant-Time Assembly at -O2
@@ -61,10 +32,9 @@ and **classification/repair** (decide whether a build leaks, and fix it if it do
 | Column | Description |
 |--------|-------------|
 | `task_name` | Sample identifier, e.g. `ct_select_1` |
-| `flag` | BinSec constant-time verdict: `secure`, `insecure`, or `unknown` -- the `x86_64` build's verdict |
-| `flag_x86_64` | BinSec verdict for the x86-64 `-O2` build |
-| `flag_aarch64_linux` | BinSec verdict for the AArch64 `-O2` build |
-| `flag_riscv` | BinSec verdict for the RISC-V `-O2` build |
+| `flag_x86_64` | BinSec constant-time verdict for the x86-64 `-O2` build: `secure`, `insecure`, or `unknown` |
+| `flag_aarch64_linux` | Same, for the AArch64 `-O2` build |
+| `flag_riscv` | Same, for the RISC-V `-O2` build |
 | `x86_64` | x86-64 assembly at -O2 (**Intel syntax**, built with `-masm=intel`) |
 | `aarch64_linux` | AArch64 assembly at -O2 |
 | `riscv` | RISC-V RV64 (`rv64gc`/`lp64d`) assembly at -O2 |
@@ -74,10 +44,11 @@ and **classification/repair** (decide whether a build leaks, and fix it if it do
 
 - **Total records**: 10
 
-| flag | count |
-|---|---|
-| `secure` | 7 |
-| `insecure` | 3 |
+| column | secure | insecure | unknown |
+|---|---|---|---|
+| `flag_x86_64` | 7 | 3 | 0 |
+| `flag_aarch64_linux` | 9 | 1 | 0 |
+| `flag_riscv` | 4 | 6 | 0 |
 
 ## The constant-time oracle
 
@@ -96,8 +67,8 @@ 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.
-This dataset's single `flag` column reports the `x86_64` build's verdict; the per-build verdicts are kept
-in `flag_x86_64`, `flag_aarch64_linux` and `flag_riscv`.
+That is why the verdict is not collapsed into one label: each target carries its own
+`flag_*` column.
 
 ## Usage
 
@@ -109,7 +80,7 @@ ds = load_dataset("Akirayasha/relbench_O2", split="test")
 record = ds[0]
 src_asm = record["x86_64"]  # source-side assembly
 tgt_asm = record["riscv"]   # reference target-side assembly
-leaky   = record["flag_riscv"] == "insecure"   # or flag / flag_x86_64 / flag_aarch64_linux
+leaky   = record["flag_riscv"] == "insecure"   # per-target verdict
 harness = record["test_c"]  # rebuild + recheck a candidate against BinSec
 ```