List view
Exit Criteria: - Submitting the final report. Deliverables: - The final report.
Due by May 15, 2026•0/1 issues closedExit Criteria: - Developers can specify more detailed requirements for contracts, indicating where to insert them into the Tower of IRs. Notably, they can pinpoint more nuanced locations, such as branches and loops. Deliverables: - A MLIR transformation library and its documentation to describe meta-contracts.
Due by May 15, 2026•0/1 issues closedExit Criteria: - Developers can relate analysis results with decompiled P-Code or other layers of the Tower of IRs. Deliverables: - A tool for aggregating and presenting verification results based on a specified layer of representation.
Due by May 15, 2026•0/1 issues closedExit Criteria: - We provide developers with an automated process to generate a verification driver for patched functions. The driver enables fuzzing or verification of the function as a standalone program. Deliverables: - Scripts to generate verification driver.
Due by November 15, 2025•0/1 issues closedExit Criteria: - We empower developers to articulate program contracts using a C-like language. Deliverables: - Description of C-like language to specify program contracts.
Due by November 15, 2025•0/1 issues closedExit Criteria: - Developers can specify more detailed requirements for patches, including insertion, deletion, or substitution of parts of the program represented in the Tower of IRs. Notably, they can pinpoint more nuanced locations, such as branches and loops. Deliverables: - A MLIR transformation library and its documentation to describe meta-patches.
Due by August 15, 2025•0/1 issues closedExit Criteria: - Developers can access the state of the patched program using intrinsics and obtain specific details about the system directly within the patch description. Deliverables: - Develop a library to access the state of the currently patched program.
Due by August 15, 2025•0/1 issues closedExit Criteria: - Developers can leverage the Patchestry API to query and describe the process of inserting patches into the Tower of IRs, specifically in simpler cases such as before/after calls.
Overdue by 2 month(s)•Due by May 15, 2025•0/1 issues closedExit Criteria: - We empower developers to articulate program patches using a C-like language. Deliverables: - Description of C-like language to specify program patch.
Overdue by 2 month(s)•Due by May 15, 2025•0/1 issues closedExit Criteria: - We empower developers to compile P-Code MLIR and seamlessly integrate it back into the binary. Deliverables: - VAST compiler plugin for generating LLVM IR from P-Code dialect.
Overdue by 5 month(s)•Due by February 15, 2025•1/1 issues closedExit Criteria: - We automate the integration of P-Code MLIR into Tower IRs, the representation used in the VAST compiler. Deliverables: - VAST compiler plugin for integrating P-Code dialect into Tower of IRs
Overdue by 5 month(s)•Due by February 15, 2025•1/1 issues closedExit Criteria: - We provide described deliverables that enable developers to generate MLIR from P-Code. Deliverables: - P-Code MLIR dialect library and a tool for generating it from decompiled P-Code
Overdue by 8 month(s)•Due by November 15, 2024•15/16 issues closed