From 694ee0b186c96d05ac30aeee3b73c312e3970cf3 Mon Sep 17 00:00:00 2001 From: Andrey Miroshnikov Date: Tue, 28 Nov 2023 17:48:17 +0000 Subject: [PATCH] Add notes on bug #980 --- meetings/sync_up/sync_up_2023-11-28.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/meetings/sync_up/sync_up_2023-11-28.mdwn b/meetings/sync_up/sync_up_2023-11-28.mdwn index fa7a01f03..1e2329316 100644 --- a/meetings/sync_up/sync_up_2023-11-28.mdwn +++ b/meetings/sync_up/sync_up_2023-11-28.mdwn @@ -27,6 +27,22 @@ - The first step is to make modifications to `svanalysis.py` to classify the RISC-V instructions. - Standard RISC-V opcode format: +- [bug #980](https://bugs.libre-soc.org/show_bug.cgi?id=980) + - A lot of work, need to focus on the basics + - Issues with current Python pseudo-code compiler: + - pseudocode is full of python-isms such as some variables are + python ints and some are selectableint and some are strings etc. + - plus, the parser currently has wrong operator precedence + [bug #1082](https://bugs.libre-soc.org/show_bug.cgi?id=1082). + - Suggested minimal goal for bug #980 is: + - Use AST (operands, flow, etc. as we already do for generated + Python func's) and a custom visitor function to convert to C code. + - Generate C functions which can be compiled without errors. + - Generated functions can be run from a main function to confirm results. + - Jacob suggested using `maddedu` as a benchmark, since it has + non-trivial pseudo-code. + - + # Dmitry -- 2.30.2