Asciidoc Artifact Generation

[IIITM-Jay]

Description

This PR deals with generating asciidoc based format in the form encoding.adoc on running upon Makefile via make command.

Approach Used

1. Created an asciidoc_utils.py script to generate the asciidoc related output
2. The make_asciidoc() function will be called in the main parse.py script
3. Made necessary and needed changes for Makefile
4. Taken reference from encoding.out.h and c_utils.py

[IIITM-Jay]

@aswaterman needed your feedback on this PR.

[AFOliveira]

Hello!
I was browsing through the PR's and I think this asciidoc output is something really great! I don't know if you have seen my previous attempts at this; initial approach is here riscv/riscv-isa-manual#1590) and this is where I ended
riscv-encodings.pdf. I think that great future additions to this PR could be the wavedrom and splitting instructions by extensions. If you want to see my approach, most of it is here . If this is well accepted, I'd be more than interested in collaborating and getting this inside this full asciidoc generation inside this repo :)

[rpsene]

.adoc is correctly generated, @aswaterman we need your input on whether the date in the .adoc is correct. I'm attaching a pdf created out of the asciidoc file created by executing make.
PS: Edited the below results (the last console for asciidoc related generation can be verified) for better visualization

Running with args : ['./parse.py', '-c', '-go', '-chisel', '-sverilog', '-rust', '-latex', '-spinalhdl', '-asciidoc', 'rv*', 'unratified/rv*']
Extensions selected : ['rv*', 'unratified/rv*']
INFO:: encoding.out.h generated successfully
INFO:: inst.chisel generated successfully
INFO:: inst.spinalhdl generated successfully
INFO:: inst.sverilog generated successfully
INFO:: inst.rs generated successfully
INFO:: inst.go generated successfully
INFO:: instr-table.tex generated successfully
INFO:: priv-instr-table.tex generated successfully
INFO:: encoding.adoc generated successfully

[rpsene]

Uploading encoding.pdf…

[IIITM-Jay]

@rpsene I think the link is broken for the pdf that you have attached, @aswaterman and @rpsene here I am attaching the same

encoding.pdf