SysY Testcase Conversion Workflow
You are an expert compiler engineer. Your goal is to convert standard C/C++ competitive programming code into Strict SysY (a simplified C subset) and generate valid test data.
Non-Negotiable Grammar Rules
Adhere to these rules strictly. Read references/sysy_lang_grammar.md only if you encounter an obscure syntax edge case not covered here.
| Feature |
Constraint |
Fix / Refactor |
| Prototypes |
Implicit |
Do NOT write int getint(); or int printf(...);. |
| Memory / Size |
Max 4MB Total (MARS Limit) |
Scale Down Constants. 1e6 $\to$ 1e4. Total int elements < 500,000. |
| Preprocessor |
BANNED (#include, #define, #ifdef) |
Use const int for constants. Delete imports. |
| Types |
int, void ONLY |
No long long, float, double, char, bool. |
| Pointers |
BANNED (int *p, &x, *ptr) |
Pass arrays as int a[]. Use return values for scalar outputs (no void f(int *res)). |
| Arrays |
1D Arrays ONLY |
Flatten int a[N][M] $\to$ int a[N*M]. No VLAs. |
| Loops |
for loops ONLY. No declarations inside () |
Move vars out: int i; for(i=0;...). No do-while. No while. turn while(1) into for(;;). |
| Returns |
Non-void funcs MUST return |
Add dummy return 0; at end of function, even after infinite loops. |
| Conditions As Values |
Exp → AddExp (arithmetic only) |
Do NOT use relational / logical expressions as values, e.g. return a < b; or x = (a < b);. Rewrite: if (a < b) return 1; return 0; or x = 0; if (a < b) x = 1;. |
| Input |
int getint() ONLY |
No scanf, cin, getchar. |
| Output |
printf ONLY |
Format string is a SysY StringConst: only %d is allowed as a format placeholder, and the only escape sequence is \n (backslash may appear only in \n). No other format specifiers/modifiers (e.g. %c, %s, %%, %05d) and no other escapes (e.g. \\, \", \t, \r, \0). Ensure the number of , Exp arguments equals the number of %d. |
| Parentheses |
PrimaryExp → '(' Exp ')' and Exp → AddExp |
(...) as an expression can wrap arithmetic only. Besides mandatory syntax like if (Cond) / for (...; Cond; ...), do NOT add extra parentheses around conditions (any `== != < > <= >= && |
| Operators |
No Bitwise (<<, >>, &, ` |
, ^`) |
| Structs |
BANNED |
Split into parallel arrays (e.g., x[N], y[N]). |
| Globals |
Encouraged for large arrays |
Prevent stack overflow in SysY runtime, keep totol size < 4MB. |
| Input Data |
Strictly 1 Integer Per Line (in.txt) |
No spaces (1 2). Must be 1\n2. Matches MIPS syscall. If testfile.txt uses a sentinel to stop reading (e.g., if (ch == 0) break;, while (x != 0), while (1) { x=getint(); if (x==0) break; }), then in.txt must explicitly include that sentinel value as the last integer. Do not rely on EOF behaving like 0: SysY MIPS getint() is implemented via syscall 5 and does not implement “EOF → 0”. |
Execution Protocol
Follow these steps sequentially.
Step 1: Initialize
Use the helper script to create the directory and placeholder files.
python3 .codex/skills/create-sysy-testcase/scripts/init_case.py <TARGET_DIR>
Step 2: Write Logic (The Intelligence Part)
Translate the source logic into Strict SysY. Focus your "thinking" here.
- Scale Down: If original code has
MAXN = 100000, change it smaller to fix up to MARS's address space limit(about 4MB). Ensure logic consistency.
- Refactor logic to fit the constraints above (e.g., flatten 2D arrays).
- Write the code to
testfile.txt.
- Write input data to
in.txt (newline-separated integers only) matching your scaled-down size. If the program reads until a sentinel (e.g., 0) rather than a known count, put that sentinel explicitly as the last integer; do not rely on EOF.
cat <<'EOF' > <TARGET_DIR>/testfile.txt
// ... your converted SysY code ...
EOF
cat <<'EOF' > <TARGET_DIR>/in.txt
// ... your input numbers ...
EOF
Step 3: Compile, Run & Verify
Use the runner script. It automatically wraps your code with C headers, compiles it (gcc/clang), runs it against in.txt, and generates ans.txt.
python3 .codex/skills/create-sysy-testcase/scripts/run_case.py <TARGET_DIR>
Step 4: Fix & Retry
If Step 3 reports a COMPILE ERROR or RUNTIME ERROR:
- Read the error output.
- Fix the logic in
testfile.txt.
- Rerun Step 3.
Translation Strategy Tips
- SysY input (
in.txt) must be newline-separated integers.
- If the original problem uses strings (e.g., "PUSH", "POP"), map them to integers (e.g., 1, 2) in your translation logic.
- MIPS Compatibility Check:
in.txt must not contain spaces between numbers.
- Never use EOF as a terminator: if the program’s input loop expects a terminator value (commonly
0, sometimes -1/-999), put that value explicitly at the end of in.txt (and keep it on its own line).
- Strengthen
in.txt slightly: prefer including a mix of small/edge values (e.g., 0/1/-1, min/max for scaled constraints) and a few typical values, while still matching the program’s expected format and counts; always end the file with a trailing newline.
1---2name: create-sysy-testcase3description: Convert C/C++ code into Strict SysY testcases using Python automation scripts.4---5
6# SysY Testcase Conversion Workflow
7
8You are an expert compiler engineer. Your goal is to convert standard C/C++ competitive programming code into **Strict SysY** (a simplified C subset) and generate valid test data.
9
10## Non-Negotiable Grammar Rules
11**Adhere to these rules strictly.** Read `references/sysy_lang_grammar.md` **only** if you encounter an obscure syntax edge case not covered here.
12
13| Feature | Constraint | Fix / Refactor |
14| :--- | :--- | :--- |
15| **Prototypes** | **Implicit** | **Do NOT** write `int getint();` or `int printf(...);`. |
16| **Memory / Size** | **Max 4MB Total** (MARS Limit) | **Scale Down Constants**. `1e6` $\to$ `1e4`. Total `int` elements < 500,000. |
17| **Preprocessor** | **BANNED** (`#include`, `#define`, `#ifdef`) | Use `const int` for constants. Delete imports. |
18| **Types** | `int`, `void` **ONLY** | No `long long`, `float`, `double`, `char`, `bool`. |
19| **Pointers** | **BANNED** (`int *p`, `&x`, `*ptr`) | Pass arrays as `int a[]`. Use **return values** for scalar outputs (no `void f(int *res)`). |
20| **Arrays** | **1D Arrays ONLY** | Flatten `int a[N][M]` $\to$ `int a[N*M]`. **No VLAs**. |
21| **Loops** | **`for` loops ONLY**. **No declarations inside `()`** | Move vars out: `int i; for(i=0;...)`. No `do-while`. No `while`. turn `while(1)` into `for(;;)`. |
22| **Returns** | **Non-void funcs MUST return** | Add dummy `return 0;` at end of function, **even after infinite loops**. |
23| **Conditions As Values** | `Exp → AddExp` (arithmetic only) | Do **NOT** use relational / logical expressions as values, e.g. `return a < b;` or `x = (a < b);`. Rewrite: `if (a < b) return 1; return 0;` or `x = 0; if (a < b) x = 1;`. |
24| **Input** | `int getint()` **ONLY** | No `scanf`, `cin`, `getchar`. |
25| **Output** | `printf` **ONLY** | Format string is a **SysY `StringConst`**: **only** `%d` is allowed as a format placeholder, and the **only** escape sequence is `\n` (backslash may appear **only** in `\n`). **No** other format specifiers/modifiers (e.g. `%c`, `%s`, `%%`, `%05d`) and **no** other escapes (e.g. `\\`, `\"`, `\t`, `\r`, `\0`). Ensure the number of `, Exp` arguments equals the number of `%d`. |
26| **Parentheses** | `PrimaryExp → '(' Exp ')'` and `Exp → AddExp` | `(...)` as an expression can wrap **arithmetic only**. Besides mandatory syntax like `if (Cond)` / `for (...; Cond; ...)`, do **NOT** add extra parentheses around conditions (any `== != < > <= >= && || !`). Rewrite via precedence/distribution, e.g. `if (t2 > 0 && (a == 42 || a == 47))` $\to$ `if (t2 > 0 && a == 42 || t2 > 0 && a == 47)`. |
27| **Operators** | No Bitwise (`<<`, `>>`, `&`, `|`, `^`) | Use arithmetic: `*2`, `/2`, `%2`. Use lookup tables. |
28| **Structs** | **BANNED** | Split into parallel arrays (e.g., `x[N]`, `y[N]`). |
29| **Globals** | Encouraged for large arrays | Prevent stack overflow in SysY runtime, keep totol size < 4MB. |
30| **Input Data** | **Strictly 1 Integer Per Line** (`in.txt`) | No spaces (`1 2`). Must be `1\n2`. Matches MIPS syscall. If `testfile.txt` uses a **sentinel** to stop reading (e.g., `if (ch == 0) break;`, `while (x != 0)`, `while (1) { x=getint(); if (x==0) break; }`), then `in.txt` must **explicitly include that sentinel value as the last integer**. **Do not rely on EOF behaving like `0`**: SysY MIPS `getint()` is implemented via `syscall 5` and does not implement “EOF → 0”. |
31
32## Execution Protocol
33
34Follow these steps sequentially.
35
36### Step 1: Initialize
37
38Use the helper script to create the directory and placeholder files.
39
40```bash
41python3 .codex/skills/create-sysy-testcase/scripts/init_case.py <TARGET_DIR>
42```
43
44### Step 2: Write Logic (The Intelligence Part)
45
46Translate the source logic into Strict SysY. Focus your "thinking" here.
47
48- **Scale Down**: If original code has `MAXN = 100000`, change it smaller to fix up to MARS's address space limit(about 4MB). Ensure logic consistency.
49- **Refactor** logic to fit the constraints above (e.g., flatten 2D arrays).
50- **Write** the code to `testfile.txt`.
51- **Write** input data to `in.txt` (newline-separated integers only) matching your scaled-down size. If the program reads until a sentinel (e.g., `0`) rather than a known count, put that sentinel **explicitly** as the last integer; do **not** rely on EOF.
52
53```bash
54cat <<'EOF' > <TARGET_DIR>/testfile.txt
55// ... your converted SysY code ...
56EOF
57
58cat <<'EOF' > <TARGET_DIR>/in.txt
59// ... your input numbers ...
60EOF
61```
62
63### Step 3: Compile, Run & Verify
64
65Use the runner script. It automatically wraps your code with C headers, compiles it (gcc/clang), runs it against `in.txt`, and generates `ans.txt`.
66
67```bash
68python3 .codex/skills/create-sysy-testcase/scripts/run_case.py <TARGET_DIR>
69```
70
71### Step 4: Fix & Retry
72
73If Step 3 reports a **COMPILE ERROR** or **RUNTIME ERROR**:
74
751. Read the error output.
762. Fix the logic in `testfile.txt`.
773. Rerun Step 3.
78
79## Translation Strategy Tips
80- SysY input (`in.txt`) must be **newline-separated integers**.
81- If the original problem uses strings (e.g., "PUSH", "POP"), map them to integers (e.g., 1, 2) in your translation logic.
82- **MIPS Compatibility Check**: `in.txt` **must not** contain spaces between numbers.
83- **Never use EOF as a terminator**: if the program’s input loop expects a terminator value (commonly `0`, sometimes `-1`/`-999`), put that value **explicitly** at the end of `in.txt` (and keep it on its own line).
84- **Strengthen `in.txt` slightly**: prefer including a mix of small/edge values (e.g., `0/1/-1`, min/max for scaled constraints) and a few typical values, while still matching the program’s expected format and counts; always end the file with a trailing newline.
majiayu000