[Libre-soc-bugs] [Bug 979] Implement C-based Power ISA decoder compiler

[bugzilla-daemon at libre-soc.org]

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

Andrey Miroshnikov <andrey at technepisteme.xyz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |andrey at technepisteme.xyz

--- Comment #56 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
(In reply to Dmitry Selyutin from comment #55)
>
> As for the tests, I actually liked the idea, and the motto of the comment
> overall was "that's The Right Thing To Do, I really missed it, thank you for
> pointing that!". I've been thinking of the following:
> 1. Standalone C executable (opid-dis), which is capable of base instruction
> decoding (just gets the raw data and outputs in some simple-ish format easy
> to parse).
> 2. Some Python test which builds the instructions, assembles them and then
> feeds to opid-dis and gets its output.
> 3. When opid-dis output is captured, the Python test compares the results to
> the expected.

If you don't mind me butting in, I really like the idea.

Because, to my understanding, all supported instructions of the disassembler
can be tested with this python script (eventually, probably
out-of-scope/unnecessary right now).

And having opid-dis as a standalone tool means it can eventually be matured to
become a full disassembler (as you have already rationalised).

> 
> 3. At some later stage, we might opt to use the same approach for the
> assembler.

Making the future work of the assembler easier by having this executable/python
test framework sounds great as well.

> I really would like to have both assembly and disassembly
> generated, adding each and every instruction to binutils manually is the
> worst choice.

I'm sure we all agree that autogenerating is better. Perhaps another task we
can allocate some funding to from one of the grants that need to be used up?

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