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.

Execution Protocol

Follow these steps sequentially.

Step 1: Initialize

Use the helper script to create the directory and placeholder files.

bash
1python3 .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.

bash
1cat <<'EOF' > <TARGET_DIR>/testfile.txt
2// ... your converted SysY code ...
3EOF
4
5cat <<'EOF' > <TARGET_DIR>/in.txt
6// ... your input numbers ...
7EOF

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.

bash
1python3 .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:

1. Read the error output.
2. Fix the logic in testfile.txt.
3. 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.