Add notes on bug #980

diff --git a/meetings/sync_up/sync_up_2023-11-28.mdwn b/meetings/sync_up/sync_up_2023-11-28.mdwn
index fa7a01f03e1d8f46799a2b0b525cece50f82d742..1e2329316a1856d4e8a0040313d18730fcbc06fe 100644 (file)
--- 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: <https://github.com/riscv/riscv-opcodes>
 
+- [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