From: Andrey Miroshnikov Date: Tue, 28 Nov 2023 17:26:38 +0000 (+0000) Subject: Add more info X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=2215a31339a061b8857a5cbf4ac29b8feee78557;p=libreriscv.git Add more info --- diff --git a/meetings/sync_up/sync_up_2023-11-28.mdwn b/meetings/sync_up/sync_up_2023-11-28.mdwn index 9c377256c..02a223a2b 100644 --- a/meetings/sync_up/sync_up_2023-11-28.mdwn +++ b/meetings/sync_up/sync_up_2023-11-28.mdwn @@ -26,13 +26,17 @@ - RISC-V example extension: - The first step is to make modifications to `svanalysis.py` to classify the RISC-V instructions. - Standard RISC-V opcode format: -- Invent an opcode format? # Dmitry * Check whether RISC-V have their own way of describing the instructions (likely they do). +* Familiarise yourself with +[svanalysis.py](https://git.libre-soc.org/?p=openpower-isa.git;a=blob;f=src/openpower/sv/sv_analysis.py;h=21778ad02d78c4f7ef5b6df93e096f4abbe365ad;hb=HEAD), +as we will need a similar tool for RISC-V. +* Check what RISC-V support in binutils looks like. *Needed for confirming +the details of the RISC-V binutils grant*. # Sadoon @@ -60,6 +64,8 @@ [bug #1183](https://bugs.libre-soc.org/show_bug.cgi?id=1183) which jacob also noted for sv.cmpi/ff needed on bigmul. +* Guide Dmitry on svanalysis.py. + # Shriya -