[libre-riscv-dev] Markdown on the wiki?
Luke Kenneth Casson Leighton
lkcl at lkcl.net
Wed Jul 15 11:47:03 BST 2020
On Wed, Jul 15, 2020 at 11:05 AM Luke Kenneth Casson Leighton
<lkcl at lkcl.net> wrote:
> On Wed, Jul 15, 2020 at 2:40 AM Samuel Falvo II <sam.falvo at gmail.com> wrote:
> > Hi Luke,
> > I wrote up a summary of what I've learned by reviewing the source
> > code. But, when I view the notes that I've written,
> > https://libre-soc.org/Documentation/notes_on_formal_proofs/
> excellent. i'll find a location for it. thank you for creating that page.
i've put some comments inline, samuel, particularly referencing the
investigation last night and this morning:
if you create a bugreport for it we can actually put in an rfp for you
(request for payment) - it's a small budget for documentation.
* the pipeline API is inviolate. you do not break it. *at no time*
will there *ever* be circumstances where it is bypassed. evverrrr.
* the only "exception" to that is LDSTCompUnit - and it achieves this
by *not using the pipeline API at all*.
* the ASCII art diagram is slightly misleading to refer to its inputs
and outputs as "Registers" because this could be confused with
* FPPipeContext (dut.o.ctx, dut.i.ctx) is not a Record. this would
have been the source of the issue you encountered
> > the formatting
> > of fixed-width code snippets enclosed in `backticks` results in the
> > snippets being on a completely new HTML division, as if I'd written
> > ```backticks``` instead.
> yes. there's a bug where fixed-width code following bullet-points
> does not get marked up as fixed-width. to sort that i had to change
> the css:
i wrote some code last week which auto-altered all of the isa
pseudocode sections - every single one of which (hundreds) had that
bug i mentioned. having "fixed" that i've removed the css "code"
More information about the libre-riscv-dev