Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 316] bperm TODO
From: bugzilla-daemon @ 2020-05-20 22:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

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

--- Comment #76 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Michael Nolan from comment #75)
> (In reply to Cole Poirier from comment #74)
> > Test passes, and code has been commit-pushed. Moving on to your suggestion
> > on today's kanban update of integrating the formal proof of bpermd:
> > 
> Cool. I've modified test_bpermd a bit so it exercises the module a bit
> better. Previously, you only had it do one iteration with two constants, and
> those constants made bpermd evaluate to 0. This isn't *really* sufficient to
> establish much confidence in the module, so I modified it to do ~20
> iterations of something that would evaluate to something other than 0. 
> 
> 
> 
> 
> > How should I go about integrating the formal proof of bpermd into the
> > logical pipeline? I've thought about it, and I am unsure as to how to
> > proceed. Is there a model I can follow as before?
> > 
> > I also want to follow up on a comment of Michael's from yesterday:
> > 
> > ```
> > From comment #50 of this bug
> > 
> > Michael Nolan 2020-05-19 20:24:19 BST
> > I'd say try hooking it up to main_stage and adding a test for it would be
> > better than trying to "optimize" the proof. Especially since there's a bug
> > in the module that the proof hasn't revealed (hint: it has to do with
> > power's numbering of bits).
> > ```
> > 
> > Is my proof of bpermd in fact not a proper proof, and incorrect because it's
> > making an mistake with endian-ness?
> 
> Well kinda. Your proof is written to match the Power ISA spec, and from a
> glance it looks like it does that. However, Power bit indices go from left
> to right, which is opposite what python and nmigen do. So although your
> proof looks like it matches the spec, it doesn't give correct results when
> it's actually tested. That's why I suggested you hook it up to the testbench
> , because the testbench compares it to some python pseudocode that *does*
> index bits correctly. 
> 
> So what I think you should do now is pull and run the testbench again, and
> see if you can't figure out how to get it to pass those tests. Then modify
> the proof correspondingly.

Thanks Michael, your help is yet again very helpful :) Unfortunately I won't be
able to do this until tomorrow morning because an exterminator appointment is
forcing me to be away from my computer. Looking forward to tackling this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 304] Define minimum viable interface set for 180nm ASIC
From: bugzilla-daemon @ 2020-05-20 22:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-304-13@https.bugs.libre-soc.org/>

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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
conversation notes from Tim (Raptor Engineering)

priority:

* 2x SPI master
* 4x I2C master
* 2x UART
* 4x LPC master
* EINT* Serialsed IRQ (LPC, from PCIe) - 15 or so IRQs, these are
PC>PCIe>OpenPower mappings

Quad SPI raptorengineering
LPC bridge github raptorengineering
~

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 316] bperm TODO
From: bugzilla-daemon @ 2020-05-20 19:53 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

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

--- Comment #75 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Cole Poirier from comment #74)
> Test passes, and code has been commit-pushed. Moving on to your suggestion
> on today's kanban update of integrating the formal proof of bpermd:
> 
Cool. I've modified test_bpermd a bit so it exercises the module a bit better.
Previously, you only had it do one iteration with two constants, and those
constants made bpermd evaluate to 0. This isn't *really* sufficient to
establish much confidence in the module, so I modified it to do ~20 iterations
of something that would evaluate to something other than 0. 




> How should I go about integrating the formal proof of bpermd into the
> logical pipeline? I've thought about it, and I am unsure as to how to
> proceed. Is there a model I can follow as before?
> 
> I also want to follow up on a comment of Michael's from yesterday:
> 
> ```
> From comment #50 of this bug
> 
> Michael Nolan 2020-05-19 20:24:19 BST
> I'd say try hooking it up to main_stage and adding a test for it would be
> better than trying to "optimize" the proof. Especially since there's a bug
> in the module that the proof hasn't revealed (hint: it has to do with
> power's numbering of bits).
> ```
> 
> Is my proof of bpermd in fact not a proper proof, and incorrect because it's
> making an mistake with endian-ness?

Well kinda. Your proof is written to match the Power ISA spec, and from a
glance it looks like it does that. However, Power bit indices go from left to
right, which is opposite what python and nmigen do. So although your proof
looks like it matches the spec, it doesn't give correct results when it's
actually tested. That's why I suggested you hook it up to the testbench ,
because the testbench compares it to some python pseudocode that *does* index
bits correctly. 

So what I think you should do now is pull and run the testbench again, and see
if you can't figure out how to get it to pass those tests. Then modify the
proof correspondingly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 19:46 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #7)

> So for this module, how would that work? I'm assuming we wouldn't be passing
> in all 8 CRs, because that would be just as bad as what we have now. But we
> need the full CR for mfcr and mtcrf. Would we have 2 small cr inputs as well
> as the full cr, and depending on whether which opcode it is we select which
> one to use?

yes basically.  perhaps even use the 32 bit path to get the smaller regs to it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 20may2020
From: Luke Kenneth Casson Leighton @ 2020-05-20 19:44 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0220ADD2-E2B5-4DEB-A7CF-3E33F506BD4F@getmailspring.com>

On Wednesday, May 20, 2020, Cole Poirier <colepoirier@gmail.com> wrote:

> On May 20 2020, at 8:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
>
> > btw as a third (incremental) step, after integrating it and putting in
> > the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
> > actually be able to integrate the formal proof into the Logical
> > pipeline as well.
>
> Will copy this to and comment on it at https://bugs.libre-soc.org/
> show_bug.cgi?id=316.


good call.


> >> > * talked with Marketnext about the resource requirements for the May
> >> > 30 Hackathon.
> >>
> >> Is there a document about this on the wiki?
> >
> > there isn't.  there should be.  however it is up to Marketnext.  the
> > issue is that i am not sure if they understand quite how high the
> > resource requirements are, and consequently how long it will take
> > people in India (and other places across the world) to install the
> > development environment.
>
> Ah that's an interesting constraint. Would it be possible (or even
> desirable) to provide them with a compressed archive of all the
> necessary repos, tools, etc in a frozen state?


this requires the organisers to understand.  they are not keenly
technical.  they love the idea.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 19:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

--- Comment #7 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #6)
> this is dreadful:
> 
>                 for i in range(4):
>                     comb += cr_out_arr[bf*4 + i].eq(cr_arr[bfa*4 + i])
> 
> the computation of the index is done almost a hundred times or more.
> 32x4 times.
> 
> for now it can be done again with a mask (shifted).  two masks - one
> to shift-extract cr[bfa*4..+4], shift by the *difference* between
> bf and bfa then bit-mask in.
> 
> dreadful.
> 
> we really need to split CR out into its 8 separate CRs.  XER's fields
> are going to have to be done this way anyway.

So for this module, how would that work? I'm assuming we wouldn't be passing in
all 8 CRs, because that would be just as bad as what we have now. But we need
the full CR for mfcr and mtcrf. Would we have 2 small cr inputs as well as the
full cr, and depending on whether which opcode it is we select which one to
use?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 316] bperm TODO
From: bugzilla-daemon @ 2020-05-20 19:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

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

--- Comment #74 from Cole Poirier <colepoirier@gmail.com> ---
Test passes, and code has been commit-pushed. Moving on to your suggestion on
today's kanban update of integrating the formal proof of bpermd:

```
Luke in reply to Cole:

>Today I plan on integrating the Bpermd module into the
>logical pipeline, with tests.

fooocuuuus :)  adding the module to Logical main_stage.py should be
around... maximum 10 lines of code.  really.  not.  difficult.  link
the inputs.  link the outputs.  err... that's it.

btw as a third (incremental) step, after integrating it and putting in
the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
actually be able to integrate the formal proof into the Logical
pipeline as well.
```

How should I go about integrating the formal proof of bpermd into the logical
pipeline? I've thought about it, and I am unsure as to how to proceed. Is there
a model I can follow as before?

I also want to follow up on a comment of Michael's from yesterday:

```
From comment #50 of this bug

Michael Nolan 2020-05-19 20:24:19 BST
I'd say try hooking it up to main_stage and adding a test for it would be
better than trying to "optimize" the proof. Especially since there's a bug in
the module that the proof hasn't revealed (hint: it has to do with power's
numbering of bits).
```

Is my proof of bpermd in fact not a proper proof, and incorrect because it's
making an mistake with endian-ness?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 19:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
this is dreadful:

                for i in range(4):
                    comb += cr_out_arr[bf*4 + i].eq(cr_arr[bfa*4 + i])

the computation of the index is done almost a hundred times or more.
32x4 times.

for now it can be done again with a mask (shifted).  two masks - one
to shift-extract cr[bfa*4..+4], shift by the *difference* between
bf and bfa then bit-mask in.

dreadful.

we really need to split CR out into its 8 separate CRs.  XER's fields
are going to have to be done this way anyway.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] daily kan-ban update 20may2020
From: Cole Poirier @ 2020-05-20 19:34 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDy9K+qhLMoet5s=_yCHp1m5ay7FcKL+VK8PVffH1axRRg@mail.gmail.com>

On May 20 2020, at 8:14 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Wed, May 20, 2020 at 3:51 PM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> Yesterday I learned another valuable lesson on the merits of the KISS
>> philosophy.
> 
> funny man :)
> 
>> Today I plan on integrating the Bpermd module into the
>> logical pipeline, with tests.
> 
> fooocuuuus :)  adding the module to Logical main_stage.py should be
> around... maximum 10 lines of code.  really.  not.  difficult.  link
> the inputs.  link the outputs.  err... that's it.
> 
> btw as a third (incremental) step, after integrating it and putting in
> the unit test into soc.fu.logical.test/test_pipe_caller.py, you should
> actually be able to integrate the formal proof into the Logical
> pipeline as well.

Will copy this to and comment on it at https://bugs.libre-soc.org/show_bug.cgi?id=316.

>> > * talked with Marketnext about the resource requirements for the May
>> > 30 Hackathon.
>> 
>> Is there a document about this on the wiki?
> 
> there isn't.  there should be.  however it is up to Marketnext.  the
> issue is that i am not sure if they understand quite how high the
> resource requirements are, and consequently how long it will take
> people in India (and other places across the world) to install the
> development environment.

Ah that's an interesting constraint. Would it be possible (or even
desirable) to provide them with a compressed archive of all the
necessary repos, tools, etc in a frozen state?

>> If not would you mind
>> briefly explaining what the parameters and the objectives of the
>> hackathon are?
> 
> to introduce over 15 different groups / teams / individuals to
> Libre-SOC development.

That's pretty darn cool!

>> > * received a message from these guys, they would like to do a review
>> > https://radicallyopensecurity.com/
>> 
>> Just took a quick perusal of their website, they look like they share
>> our philosophy about digital rights, as well as having a
>> 'social-benefit-esque' organizational model. I think their doing a
>> review of our processor's security would be welcome help. Your thoughts?
> 
> their review is a mandatory requirement as part of the NLNet funding.
> i did point out to them that asking to have a private conversation
> about their role is not exactly very transparent :)
> 
> l.

Oh, very happy that this turns out to be a mandatory NLNet funding
requirement. I agree that their request for private conversation is odd
given the context.

Cole


_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-20 19:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-305-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=332

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-20 19:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=305

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 198] Formal correctness proofs are needed for low-level libraries in LibreSOC
From: bugzilla-daemon @ 2020-05-20 19:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-198-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   budget (EUR) for|7850                        |7650
 completion of task|                            |
   (excludes budget|                            |
       allocated to|                            |
          subtasks)|                            |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-20 19:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 total budget (EUR)|0                           |200
  for completion of|                            |
       task and all|                            |
           subtasks|                            |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-20 19:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    parent task for|                            |198
  budget allocation|                            |

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-20 19:27 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    NLnet milestone|---                         |NLNet.2019.10.Formal

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 332] Formal correctness proof needed for CR pipeline
From: bugzilla-daemon @ 2020-05-20 19:26 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-332-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lkcl@lkcl.net

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
* OP_CROP proof -
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=16ac8bcd32bd2998d58488ca236f8ff721eccaf6
* OP_MTCRF proof -
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=7d16e4157873bb5ad17c0bb9a0d646b15b0e2b1b

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] monorepo
From: Luke Kenneth Casson Leighton @ 2020-05-20 19:17 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzNSnoGjkWFrZu6Rm96Pr5w+w8t=tbisRLUJNnUaMZ0KA@mail.gmail.com>

sorry jacob: i could put it better: we are however really seriously
pushed for time.

the context-switch of the discussion itself, the disruption of a
massive organisational change, the reorganisation of the entire
website and all documentation, the scripts, the LIP6.fr scripts which
Jean-Paul wrote which rely on the repository layouts: these are
*massive* ramifications far beyond any of the "benefits" of something
that some high-profile quotes great quotes project happens to impose
on its users for their own personal convenience (llvm).

the answer is and remains a firm "no", due to the detrimental short
*and* long-term consequences and implications.

sorry.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] monorepo
From: Luke Kenneth Casson Leighton @ 2020-05-20 19:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5ERSGx8TkYjQ2=Gk29Qfn-a1DqtSVAjS73pBp1AG5qDA@mail.gmail.com>

On Wed, May 20, 2020 at 7:43 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> what about if we have a monorepo where we have an automatically updated
> read-only git mirrors for the subdirectories that can be used independently
> as well as documenting that everywhere it's relevant? That would quite
> explicitly give the message that those subdirectories are intended to be
> usable separately from the rest of our code.

again: bear in mind that this is a non-essential administrative task -
one that even the discussion itself is a distraction.

to evaluate this idea - its viability to ensure that commits for the
correct portions of the monorepo are preserved - is itself a
distraction.

to *code* such a system is itself a distraction.

and also not a good idea.  how do you preserve commit history when two
files in different repo-mirrors are under the same commit?

answer: you don't.

question: how do you ensure that the commit checksum is the same
across the two repositories?

answer: you don't.

git mirrors are *exact* mirrors.

all of this is a serious distraction and we do not need distractions right now.

i have been doing software development now for almost 25 years: please
trust me when i say that a monorepo is detrimental to our project's
long-term goals.

for the "inconvenience" we have to tolerate, we end up with
strategically much more useful code, with CLEAR delineation and
boundaries between each repository.

please can we stop discussing this: the answer is no, and having to
explain it each and every time is a major distraction.


> > when you have time, look up the nightmare of freeswitch ignoring standard
> > development practices when it comes to dependency management.
> >
>
> I'm not advocating for us to have all external dependencies be a part of
> our monorepo, only the code we are actively developing and is closely
> related: nmutil, soc, ieee754fpu,

closely related only because we happen to be the only users of these
repositories... *at the moment*.

> and probably the layout code.

we discussed this with jean-paul, he advises very strongly not to do that.


l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 319] POWER9 setting carry (and other) XER flags
From: bugzilla-daemon @ 2020-05-20 18:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-319-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=333

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 18:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=319

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 18:59 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|---                         |High

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
cut it down drastically by not using an Array.  sigh.  they were so good,
too.

the cr_out_array is still producing a full crossbar.  it's dreadful.
given that we have to do that reg-splitting for XER, i'm inclined to
suggest we do the same here, and to have inputs and outputs as
crN, indexed, selected and routed *externally* like RA, RB, RC and RT/RS.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 18:52 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
took a look: it takes *30 seconds* to process the graphviz.  that's a baaad
sign.

when it finally showed up, it's a full crossbar.  wark-wark...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 316] bperm TODO
From: bugzilla-daemon @ 2020-05-20 18:46 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

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

--- Comment #73 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #72)
> > Yes, has caused an hour of headache. decoder/all.py is needed in order to
> > run the tests. all.py is auto-generated, so is not present in the directory.
> > How am I supposed to auto-generate it?
> 
> ah - you should have asked earlier :)  look in the Makefile:
>     python3 src/soc/decoder/pseudo/pywriter.py

Aha! I completely forgot about the Makefile.

> > Is it supposed to be autogenerated by
> > the test itself?
> 
> no because it takes a good couple of minutes to go over the 300+ pseudo-code
> code-fragments.
> 
> > This would be odd as the
> > fu/logical/tests/test_pipe_caller.py file imports this at the top of the
> > file. Essentially, help I am quite stuck after trying to solve this for an
> > hour.
> 
> should have asked earlier :)

Indeed, I'm trying to balance doing things without help at every step, with
trying to communicate in the manner necessary for collaborative work. Getting
one step closer to the right balance with each mistake! At least this bug
report will be helpful to new members, as it's an utter novice (me) discovering
all (well, most) of the possible difficulties/misunderstandings :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 333] investigate why CR pipeline code took 100% CPU and locked up generating ILANG
From: bugzilla-daemon @ 2020-05-20 18:45 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-333-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
reduces ilang size slightly but not a lot.  need to view the graph (on
a different computer)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] monorepo
From: Jacob Lifshay @ 2020-05-20 18:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-313-13-nx9xkevLxf@https.bugs.libre-soc.org/>

On Tue, May 19, 2020, 14:41 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=313
>
> --- Comment #29 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> (In reply to Jacob Lifshay from comment #28)
> > (In reply to Michael Nolan from comment #27)
>
> > > Yep... I haven't had that happen to me yet, but it's pissing me off
> too.
> >
> > We definitely should move to a monorepo
>
> no.  that sends the wrong message, unfortunately [it says, very loudly,
> "other
> specific focussed alternative uses for our work not welcome, in the
> slightest.
> download our monorepo containing everything you don't want or need, and
> like
> it.  or Go Home.  we don't care"]
>

what about if we have a monorepo where we have an automatically updated
read-only git mirrors for the subdirectories that can be used independently
as well as documenting that everywhere it's relevant? That would quite
explicitly give the message that those subdirectories are intended to be
usable separately from the rest of our code.

>
> when you have time, look up the nightmare of freeswitch ignoring standard
> development practices when it comes to dependency management.
>

I'm not advocating for us to have all external dependencies be a part of
our monorepo, only the code we are actively developing and is closely
related: nmutil, soc, ieee754fpu, and probably the layout code. nmigen (and
maybe corolis2) would be a submodule since it often changes and is not part
of libre-soc, everything else doesn't change that often and doesn't need to
be synchronized with our code.

>
> the intention of having the csv and isatables in the wiki is to make it
> clear
> that they are independently useable *outside* of our project.
>

they would be mirrored to their own git repo (we wouldn't need the weird
.text extension), we could also mirror them to the wiki if desired.

>
> without requiring gigabyte additional downloads and dependencies which we
> need
> but they most certainly do not.
>
having separate git mirrors would make it unnecessary to download all our
code to use some portion of it.

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

page:   latest

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git