test: more test cases

[hsqStephenZhang]

I think it might be good to integrate kecc-public's testsuite here. It covers most basic cases. I could make a PR if it's wanted.

[MaxXSoft]

Do you mean the fuzzer? Or other test cases I'm unaware of?

[hsqStephenZhang]

Sorry I did not make myself clear, I meant some testsuite like llvm-test-suite, for example https://github.com/kaist-cp/kecc-public/tree/main/examples, this one might suite koopa well for educational purpose.

I could also investigate if Csmith could be integrated.

[MaxXSoft]

It's a great idea to integrate more test cases for IR, but this may require you to spend more effort selecting test cases that meet Koopa IR's requirements, which is time consuming.

I would be very happy and grateful if you could do so! If you encounter any problems, feel free to ask me for help.

[hsqStephenZhang]

Hi, I created a testsuite by kira-rs, it's based on the kecc-public's testsuite I mentioned before, with only few ruled out. Currently, I had put it in my own repo: https://github.com/hsqStephenZhang/kira-rs/tree/test/testsuite/examples.

What's the next step that you preferred? Should I add some larger and meaningful programs? And where to put these examples, Maybe a separate repo? Maybe it could be useful to compare the interpeter's output with clang's output of the same case to tell student the difference(that's what kecc-public did)

[hsqStephenZhang]

Just saw https://github.com/pku-minic/compiler-dev-test-cases.

[MaxXSoft]

Currently, I had put it in my own repo: https://github.com/hsqStephenZhang/kira-rs/tree/test/testsuite/examples.

I noticed that some test cases in kecc-public have been removed (e.g., struct.c), while some test cases have been retained but their content has been replaced with int main() { return 0; } (e.g., pointer.c).

Why does this difference exist? Can we just remove test cases like pointer.c?

Should I add some larger and meaning programs?

Some of large programs has already been covered in performance test. Therefore, this part is not a high priority.

For functional test, the focus is on covering as many corner cases as possible in the compiler/IR library, and trying to make the tests orthogonal to other functional test cases.

And where to put these examples, Maybe a separate repo?

Separate repo is okay. You can refer to pku-minic/compiler-dev-test-cases, attach .out files and .in files (if any) for each test cases.

Maybe it could be useful to compare the interpeter's output with clang's output of the same case to tell student the difference(that's what kecc-public did)

That's what .out and .in files for.