CSE340 C++ Compiler Assistance
Budget: $30 – $250 USD
I’m finishing up a compiler for my CSE340 course and need an extra pair of hands to take it across the line in C++. The project must read source code that follows the exact grammar in my PDF, build a linked-list of InstructionNode structures as its intermediate representation, and compile cleanly alongside the provided execute.cc / execute.h driver.
Where I stand
• The lexical scanner is in place and the basic framework for intermediate-code generation already works.
• The stumbling block is fleshing out full support for every statement form—assignment, input, output, if-else, while, switch, and for—so the IR nodes chain together exactly as the spec shows.
What I’ll hand over
– The full grammar & semantic rules PDF
– My current code base (VS Code / g++ friendly)
– execute.cc and execute.h used by my instructor for automated grading
What I need back
1. A completed parser and code-generation layer that handles every statement type with correct control-flow linking.
2. Clean compilation with the supplied driver (no warnings with ‑Wall preferred).
3. A short README highlighting build commands and any design notes.
I test with several instructor samples; the solution is done when each program produces the correct outputs through execute.cc.
If you’ve built miniature compilers or worked with recursive-descent / LL grammars in C++, this should feel familiar. Let me know your turnaround time and any clarifying questions—happy to jump on a quick call or share snippets to get you started.
Where I stand
• The lexical scanner is in place and the basic framework for intermediate-code generation already works.
• The stumbling block is fleshing out full support for every statement form—assignment, input, output, if-else, while, switch, and for—so the IR nodes chain together exactly as the spec shows.
What I’ll hand over
– The full grammar & semantic rules PDF
– My current code base (VS Code / g++ friendly)
– execute.cc and execute.h used by my instructor for automated grading
What I need back
1. A completed parser and code-generation layer that handles every statement type with correct control-flow linking.
2. Clean compilation with the supplied driver (no warnings with ‑Wall preferred).
3. A short README highlighting build commands and any design notes.
I test with several instructor samples; the solution is done when each program produces the correct outputs through execute.cc.
If you’ve built miniature compilers or worked with recursive-descent / LL grammars in C++, this should feel familiar. Let me know your turnaround time and any clarifying questions—happy to jump on a quick call or share snippets to get you started.