[Libre-soc-isa] [Bug 1048] OPF ISA External RFC ls011 - Fixed and Floating point LD/ST-with-update EXT2xx instructions

[bugzilla-daemon at libre-soc.org]

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

--- Comment #25 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
(In reply to Luke Kenneth Casson Leighton from comment #24)
> fanntastic. it comes out really well at the wiki page, already.
> hmmm should probably put some \section breaks in it somehow,
> or to the python "rewriter" program at least add an extra "#"
> in front of the sections.
> 
> let me deal with that, the inline "hook" into 
> 
> https://git.libre-soc.org/?p=libreriscv.git;a=blob;f=openpower/pandoc_img.py;
> hb=HEAD
Yeah, I only noticed the sections not being under the top-level heading when I
moved the inline import to earlier part of ls011 (see below).
Didn't see any activity, and git history doesn't show changes to pandoc_img.py.
I'm guessing you've been working on other tasks.

> ok so this is *required* for the submission on what i call
> "radio button 3" RFC submissions, as it s R-B-3 that will
> *actually* go into the *actual* Power ISA spec.
Ok, makes sense. For this task not needed, but in future when we get to R-B-3,
it will massively reduce the documentation maintenance.

> basically yes, they go.  i only had them as placeholders to show the
> principle,
Removed the following entries from ls011.mdwn:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=368583227251abba9ec40a1050557d1944d9feda

(already present in openpower/isa/pifixedload.mdwn)

- lbzup
- lbzupx
- lhzup
- lhzupx
- lhaup
- lhaupx
- lwzup
- lwzupx
- lwaupx
- ldup
- ldupx

In addition, I've moved the inline import to the part of ls011.mdwn where these
duplicate entries resided:
https://git.libre-soc.org/?p=libreriscv.git;a=commitdiff;h=0c319b52f5e57d5dac660da37f53f3227d97ec23


I'll proceed with the removing other duplicate entries in the same way I did
with the Load with Post-Update.


> maintained the summary table so as not to forget but also
> to have some idea of number of instructions.
A note for later work: it would be useful if the instruction list (the summary
list at the top of ls011) could be autogenerated. I'm guessing a pandoc py
filter could be used to scan the inline markdown files.
Something like detecting the following 5-line structure:

```
# [INSTRUCTION NAME]

[FORM TYPE]-Form

* [instruction] [args]
```

and producing an entry in the lsXX.mdwn file like this:

[instruction],    [rfc name], high, PO, yes, EXT2xx, no, [inline filename],
1R2W

(This is just a thought that came to me now, so I didn't explore it thoroughly,
and have checked how the other parameters like the "high", "PO", "EXT2xx" etc.
could be deduced.)
(I also seem to remember tables like this being generated during one of
previous rfc submissions, just forgotten where it was.)

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