[Libre-soc-bugs] [Bug 578] python-based svp64 "generator" class

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=578

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
see 
https://libre-soc.org/irclog/%23libre-soc.2021-01-22.log.html

lkcl> lxo: ping.
<lkcl> question for you: would you be happy to do a python-based "translator"
from binutils-style svp64 syntax into ".long 0xnnnnn; opcodev3.0b"?
<lkcl> it's for use in the unit tests like this:
<lkcl>
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/alu/test/test_pipe_caller.py;h=92c12f632fdea9b382fdb18d2f7d00200fb39fa1;hb=3518c40bb13ea2c5bb036045afadf19bb04fc270#l54
<lkcl> so that would be:
<lkcl> lst = SVP64translator(["sv.extsw r3.v, r0.s"])
<lkcl> and the output would be:
<lkcl> [".long 0xnnnnn", "extsw 3, 0"]
<lkcl> the context needs to be "picked up" - the mode - unfortunately - by
doing a lookup in the CSV output from the deduped opcodes program sv_analyse.py
<lkcl> https://libre-soc.org/openpower/opcode_regs_deduped/
<lkcl> end of this file
https://git.libre-soc.org/?p=libreriscv.git;a=blob;f=openpower/sv_analysis.py;hb=HEAD
<lkcl> and the SVP64translator can read those CSV files, create a dictionary by
assembly-code name (first column in the CSV file) and look that up to find what
the "mode" is, EXTRA2 or EXTRA3 etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.