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  0:31 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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #55 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Cole Poirier from comment #54)
> Ah yes, appreciated, I will grep first in the future. For clarification, the
> way to run the tests is by cd'ing to the soc/decoder directory then running
> 'python3 test/{test_file.py}' for each of the files in the tests directory?
> Or do I cd to the top level soc directory, and run 'sudo python3 setup.py
> test'?

Definitely don't use `sudo`. I cd to the top level and run either `python3
setup.py test` or `nosetests`.

-- 
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 323] create POWER9 MUL pipeline
From: bugzilla-daemon @ 2020-05-20  0:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-323-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=a60febdeb1c572a4b85b410c6519383fc581732d

i moved mul operations over to a MUL Function Unit.  the unit test,
test_pipe_caller.py, when cookie-cut copied over, should then be changed:

                    fn_unit = yield pdecode2.e.fn_unit
                    self.assertEqual(fn_unit, Function.SHIFT_ROT.value)

to:

                    fn_unit = yield pdecode2.e.fn_unit
                    self.assertEqual(fn_unit, Function.MUL.value)

really we should look at some point at deriving a class to contain
the common code from all these tests, soc.fn.*.test.test_pipe_caller.py

-- 
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  0:40 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 #56 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jacob Lifshay from comment #55)
> (In reply to Cole Poirier from comment #54)
> > Ah yes, appreciated, I will grep first in the future. For clarification, the
> > way to run the tests is by cd'ing to the soc/decoder directory then running
> > 'python3 test/{test_file.py}' for each of the files in the tests directory?
> > Or do I cd to the top level soc directory, and run 'sudo python3 setup.py
> > test'?
> 
> Definitely don't use `sudo`. I cd to the top level and run either `python3
> setup.py test` or `nosetests`.

I tried doing that but it seems like because the egg_info or wheel is installed
(per the HDL_Workflow instructions) within sudo bash I can't run it as a normal
user:

```
cole@computer:~/src/soc$ python3 setup.py test
running test
running egg_info
error: [Errno 13] Permission denied
```

If there is something I have to do our could due to fix this please let me
know.

In the process of running 'sudo (i know it's bad) python3 setup.py test' I
noticed some tests are failing due to import errors after the recent 'fu'
directory structure change, so I'm going through and fixing the import paths.

-- 
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  0:44 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 #57 from Cole Poirier <colepoirier@gmail.com> ---
Upon further investigation the import errors appear to be non-trivial to fix so
I am leaving them alone and moving on to adding Bpermd to fu/logical

-- 
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  0:48 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 #58 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #55)
> (In reply to Cole Poirier from comment #54)
> > Ah yes, appreciated, I will grep first in the future. For clarification, the
> > way to run the tests is by cd'ing to the soc/decoder directory then running
> > 'python3 test/{test_file.py}' for each of the files in the tests directory?

because i run ctags in one directory (usually the top level or close to it)
and stay there.

i generally run e.g. python3 fu/alu/test/test_pipe_caller.py or something.
constantly doing "cd" i find very annoying.

to find previously-run commands is a matter of running "history" followed by
!inserthistorynumber

this saves typing the command out repeatedly - also very annoying.

lots of annoyingness... :)

> > Or do I cd to the top level soc directory, and run 'sudo python3 setup.py
> > test'?
> 
> Definitely don't use `sudo`.

yep.  it will result in test output that, on return as the ordinary user,
you will not be able to overwrite.  to "fix" that, do this:

soc/src$ sudo bash
soc/src# chown -R colepoirier .
soc/src# exit
soc/src$

that will ensure that all files are owned by you (not root) in the entire soc
locally checked out repository.

a "dumb" way to achieve the same effect is to completely destroy the entire
checkout.  this is wasteful of both time and bandwidth.

> I cd to the top level and run either `python3 setup.py test` or `nosetests`.

this runs every single test, which consumes a lot of time however is a good
idea.

to get a "faster development cycle" i tend to run only the test that is needed.
delays in that cycle - by running tests that have nothing to do with the task
at
hand - i also find annoying.

however *after* that fast-iterative cycle (explicitly running only the relevant
test), it is kinda important to run more (nosetests3, python3 setup.py test)
just
to make absolutely sure you didn't break anything unrelated.  don't tell no-one
i tend not to do that very often... :)

-- 
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  0:50 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 #59 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #57)
> Upon further investigation the import errors appear to be non-trivial to fix
> so I am leaving them alone

que? que? give me a hint, i can take a look.

> and moving on to adding Bpermd to fu/logical

ok.

-- 
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 327] New: Don't use sudo with setup.py
From: bugzilla-daemon @ 2020-05-20  0:54 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 327
           Summary: Don't use sudo with setup.py
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: programmerjake@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

The HDL Workflow page should be fixed to *NOT* use sudo when calling setup.py,
instead, either use a venv (preferred) or install to the local user account.
This avoids creating files owned by root in the source directory, avoiding the
need to run all code using sudo. This also makes it possible for people stuck
with shared computers where they don't have sudo privileges to be able to
run/develop our code.

-- 
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  0:56 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 #60 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #58)
> (In reply to Jacob Lifshay from comment #55)
> > (In reply to Cole Poirier from comment #54)
> > > Ah yes, appreciated, I will grep first in the future. For clarification, the
> > > way to run the tests is by cd'ing to the soc/decoder directory then running
> > > 'python3 test/{test_file.py}' for each of the files in the tests directory?
> 
> because i run ctags in one directory (usually the top level or close to it)
> and stay there.
> 
> i generally run e.g. python3 fu/alu/test/test_pipe_caller.py or something.
> constantly doing "cd" i find very annoying.
> 
> to find previously-run commands is a matter of running "history" followed by
> !inserthistorynumber
> 
> this saves typing the command out repeatedly - also very annoying.
> 
> lots of annoyingness... :)

Ah that sounds radically better than my 'dumb' bog-standard online/corporate
unix training method of cd .. cd cd cd cd ..... ahhhh!!! I'll have to do a
quick read of what ctags is and how to use it as you've specified tomorrow. And
go back and reference your email to me from march that outlined how I could set
up my computer as you have yours set up.

> > > Or do I cd to the top level soc directory, and run 'sudo python3 setup.py
> > > test'?
> > 
> > Definitely don't use `sudo`.
> 
> yep.  it will result in test output that, on return as the ordinary user,
> you will not be able to overwrite.  to "fix" that, do this:
> 
> soc/src$ sudo bash
> soc/src# chown -R colepoirier .
> soc/src# exit
> soc/src$
> 
> that will ensure that all files are owned by you (not root) in the entire soc
> locally checked out repository.
> 
> a "dumb" way to achieve the same effect is to completely destroy the entire
> checkout.  this is wasteful of both time and bandwidth.

Perfect. Worked.

> > I cd to the top level and run either `python3 setup.py test` or `nosetests`.
> 
> this runs every single test, which consumes a lot of time however is a good
> idea.
> 
> to get a "faster development cycle" i tend to run only the test that is
> needed.
> delays in that cycle - by running tests that have nothing to do with the
> task at
> hand - i also find annoying.
> 
> however *after* that fast-iterative cycle (explicitly running only the
> relevant
> test), it is kinda important to run more (nosetests3, python3 setup.py test)
> just
> to make absolutely sure you didn't break anything unrelated.  don't tell
> no-one
> i tend not to do that very often... :)

Hmm will try to do as you preach not as you practice then :)

-- 
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  1:02 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 #61 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #59)
> (In reply to Cole Poirier from comment #57)
> > Upon further investigation the import errors appear to be non-trivial to fix
> > so I am leaving them alone
> 
> que? que? give me a hint, i can take a look.

found them.  sorted several.

-- 
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  1:04 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 #62 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #58)
> (In reply to Jacob Lifshay from comment #55)
> > (In reply to Cole Poirier from comment #54)
> > > Ah yes, appreciated, I will grep first in the future. For clarification, the
> > > way to run the tests is by cd'ing to the soc/decoder directory then running
> > > 'python3 test/{test_file.py}' for each of the files in the tests directory?
> 
> because i run ctags in one directory (usually the top level or close to it)
> and stay there.
> 
> i generally run e.g. python3 fu/alu/test/test_pipe_caller.py or something.
> constantly doing "cd" i find very annoying.
> 
> to find previously-run commands is a matter of running "history" followed by
> !inserthistorynumber
> 
> this saves typing the command out repeatedly - also very annoying.
> 
> lots of annoyingness... :)

At the bash prompt, type Ctrl-R then some portion of the previous command, it's
the readline shortcut for search through history from most to least recent. You
can also keep pressing Ctrl-R to go to the previous occurrence.

> 
> however *after* that fast-iterative cycle (explicitly running only the
> relevant
> test), it is kinda important to run more (nosetests3, python3 setup.py test)
> just
> to make absolutely sure you didn't break anything unrelated.  don't tell
> no-one
> i tend not to do that very often... :)

should do it more often, since otherwise stuff never gets fixed. Part of why I
went to lots of effort to get CI setup and working (which still needs someone
to finish setting up the CI mailing list and the sendmail script for use with
gitlab-ci-archiver).

-- 
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  1:04 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 #63 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #59)
> (In reply to Cole Poirier from comment #57)
> > Upon further investigation the import errors appear to be non-trivial to fix
> > so I am leaving them alone
> 
> que? que? give me a hint, i can take a look.

I must stop for today. I don't have confidence that I can write the necessary
code with the level of care necessary at this point at the end of my day, so I
will refrain from doing so and continue tomorrow with integrating Bpermd into
fu/logical. Below is the failed test info that I got when trying to fix import
errors in two of the tests.


Tried to fix the following two tests (stack traces provided for debuggability):
```
Failed test1:
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem2_fu_matrix.py",
line 20, in <module>
    from ..experiment.score6600 import IssueToScoreboard, RegSim, instr_q,
wait_for_busy_clear, wait_for_issue, CompUnitALUs, CompUnitBR, CompUnitsBase
  File "/home/colepoirier/src/soc/src/soc/experiment/score6600.py", line 17, in
<module>
    from soc.experiment.compalu import ComputationUnitNoDelay
  File "/home/colepoirier/src/soc/src/soc/experiment/compalu.py", line 9, in
<module>
    from soc.experiment.alu_hier import CompALUOpSubset
  File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20, in
<module>
    from soc.alu.alu_input_record import CompALUOpSubset
ModuleNotFoundError: No module named 'soc.alu'

Failed test 2:
File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem_fu_matrix.py", line
24, in <module>
    from ..experiment.score6600 import IssueToScoreboard, RegSim, instr_q,
wait_for_busy_clear, wait_for_issue, CompUnitALUs, CompUnitBR
  File "/home/colepoirier/src/soc/src/soc/experiment/score6600.py", line 17, in
<module>
    from soc.experiment.compalu import ComputationUnitNoDelay
  File "/home/colepoirier/src/soc/src/soc/experiment/compalu.py", line 9, in
<module>
    from soc.experiment.alu_hier import CompALUOpSubset
  File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20, in
<module>
    from soc.alu.alu_input_record import CompALUOpSubset
ModuleNotFoundError: No module named 'soc.alu'
```

Fixing the path of soc.alu to be soc.fu.alu results in the tests still failing
but with a different error:

```
Failed test 1:
ERROR: soc.scoreboard.test_mem2_fu_matrix.test_mem_fus
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem2_fu_matrix.py",
line 585, in test_mem_fus
    vcd_name='test_mem_fus.vcd')
  File "/home/colepoirier/src/nmigen/nmigen/compat/sim/__init__.py", line 22,
in run_simulation
    fragment.domains += ClockDomain("sync")
AttributeError: 'MemFunctionUnits' object has no attribute 'domains'

Failed test2:
ERROR: soc.scoreboard.test_mem_fu_matrix.test_mem_fus
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/colepoirier/src/soc/src/soc/scoreboard/test_mem_fu_matrix.py",
line 679, in test_mem_fus
    vcd_name='test_mem_fus.vcd')
  File "/home/colepoirier/src/nmigen/nmigen/compat/sim/__init__.py", line 22,
in run_simulation
    fragment.domains += ClockDomain("sync")
AttributeError: 'MemFunctionUnits' object has no attribute 'domains'
```

-- 
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  1:05 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 #64 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #60)

> Ah that sounds radically better than my 'dumb' bog-standard online/corporate
> unix training method of cd .. cd cd cd cd .....

you'll be hilariously amused that when presented with a DOS prompt that's
exactly what i end up doing...

> ahhhh!!! I'll have to do a
> quick read of what ctags is and how to use it as you've specified tomorrow.
> And go back and reference your email to me from march that outlined how I
> could set up my computer as you have yours set up.

be prepared to have your brain melted
> > yep.  it will result in test output that, on return as the ordinary user,
> > you will not be able to overwrite.  to "fix" that, do this:
> > 
> > soc/src$ sudo bash
> > soc/src# chown -R colepoirier .
> Perfect. Worked.

goood.

> > to make absolutely sure you didn't break anything unrelated.  don't tell
> > no-one
> > i tend not to do that very often... :)
> 
> Hmm will try to do as you preach not as you practice then :)

and what happened? i made some commits, changing stuff - e.g. renamed
Logical ALUInputData to LogicalInputData and the unit tests broke.
yaaay

-- 
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  1:07 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 #65 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #63)
> (In reply to Luke Kenneth Casson Leighton from comment #59)
> > (In reply to Cole Poirier from comment #57)
> > > Upon further investigation the import errors appear to be non-trivial to fix
> > > so I am leaving them alone
> > 
> > que? que? give me a hint, i can take a look.
> 
> I must stop for today. I don't have confidence that I can write the
> necessary code with the level of care necessary at this point at the end of
> my day,

yep.  focus. not your problem.  my responsibility.  i broke em, therefore i fix
em.

> so I will refrain from doing so and continue tomorrow with
> integrating Bpermd into fu/logical.

yep.  this one is your responsibility.

>   File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20,
> in <module>
>     from soc.alu.alu_input_record import CompALUOpSubset
> ModuleNotFoundError: No module named 'soc.alu'

sorted that one 5 mins ago

>   File "/home/colepoirier/src/soc/src/soc/experiment/alu_hier.py", line 20,
> in <module>
>     from soc.alu.alu_input_record import CompALUOpSubset
> ModuleNotFoundError: No module named 'soc.alu'
> ```

and that one.  do a git pull

> Failed test2:
> ERROR: soc.scoreboard.test_mem_fu_matrix.test_mem_fus

interesting.  ignore it.   not your problem.  do raise a separate bugreport
about it though.

-- 
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  1:09 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 #66 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Jacob Lifshay from comment #62)
> At the bash prompt, type Ctrl-R then some portion of the previous command,
> it's the readline shortcut for search through history from most to least
> recent. You can also keep pressing Ctrl-R to go to the previous occurrence.

Appreciate the tip Jacob.

> > however *after* that fast-iterative cycle (explicitly running only the
> > relevant
> > test), it is kinda important to run more (nosetests3, python3 setup.py test)
> > just
> > to make absolutely sure you didn't break anything unrelated.  don't tell
> > no-one
> > i tend not to do that very often... :)
> 
> should do it more often, since otherwise stuff never gets fixed. Part of why
> I went to lots of effort to get CI setup and working (which still needs
> someone to finish setting up the CI mailing list and the sendmail script for
> use with gitlab-ci-archiver).

Was that task assigned to Jock? I remember I helped with the initial setup but
I thought I remembered Jock taking over once the CI mailing list task was
introduced. Jacob, is there any testing stuff that I was supposed to do that
you've noticed I forgot or failed to do? I don't think there is, but honestly I
forget, as I moved on to focusing on the coriolis chroot setup script
immediately after that.

-- 
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  1:13 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 #67 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #65)
> > Failed test2:
> > ERROR: soc.scoreboard.test_mem_fu_matrix.test_mem_fus
> 
> interesting.  ignore it.   not your problem.  do raise a separate bugreport
> about it though.

Did a git pull, and now the test fails with the second error state instead of
the first. I'm not sure how I would file a bug report for this failed test, and
since this is your domain, and I have no more energy today I'll leave it to
you, ok?

-- 
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  1:34 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 #68 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #67)

> Did a git pull, and now the test fails with the second error state instead
> of the first.

joy.

> I'm not sure how I would file a bug report for this failed
> test, and since this is your domain, and I have no more energy today I'll
> leave it to you, ok?

ok :)  2:30am here so definitely time to stop.

l.

-- 
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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-05-20  3:09 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

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

--- Comment #16 from Cesar Strauss <cestrauss@gmail.com> ---
I'll now proceed to improve the unit test for LDSTCompUnit.

I'll take into account your several ideas in comment #11.

Some of my own ideas are:

1) The test driver should only present data during a single cycle, coincident
with the activation of "go". This detects data being latched at the wrong time.

2) Add some behavioral assertions.
For instance, busy_o must rise if, and only if, issue_i was active on the
previous clock.
Likewise "rel" signals must go low if, and only if, the corresponding "go" was
active on the previous clock.
And so on.
There could be a simulation "process" monitoring these kind of conditions. Or,
using nMigen assertions, and/or formal verification. I must find out more about
this.

I still need to study the interface and functionality of the L0CacheBuffer.

Regards,
Cesar

-- 
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 318] fix LDSTCompUnit
From: bugzilla-daemon @ 2020-05-20  3:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-318-13@https.bugs.libre-soc.org/>

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

--- Comment #17 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cesar Strauss from comment #16)
> I'll now proceed to improve the unit test for LDSTCompUnit.
> 
> I'll take into account your several ideas in comment #11.
> 
> Some of my own ideas are:
> 
> 1) The test driver should only present data during a single cycle,
> coincident with the activation of "go". This detects data being latched at
> the wrong time.

oh yeh, really good point.

> 
> 2) Add some behavioral assertions.
> For instance, busy_o must rise if, and only if, issue_i was active on the
> previous clock.
> Likewise "rel" signals must go low if, and only if, the corresponding "go"
> was active on the previous clock.
> And so on.

i believe these kinds of things are what Formal Proofs are for.  in particular,
when you use Past() to assert things from previous cycles.

> There could be a simulation "process" monitoring these kind of conditions.
> Or, using nMigen assertions, and/or formal verification. I must find out
> more about this.

bug 316, look up the formal_bperm.py code.  it's really well documented.

> I still need to study the interface and functionality of the L0CacheBuffer.

i tried two LDs in the score6600 code - they failed.  the first place to check
is the [prototype] L0CacheBuffer, with a twin-process.

-- 
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 319] POWER9 setting carry (and other) XER flags
From: bugzilla-daemon @ 2020-05-20  4:10 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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ah.  right.  ok.  in alu/output_stage.py the Data ok for cr0 and the XER fields
do, ov, ov32, need to be set based on  Rc and OE from the instruction.

CR0                     (if Rc=1)
SO OV OV32             (if OE=1)

this code shows that the op.carry_out field from op decode is Rc

and that op.oe is likewise OE.



carry_32 := result(32) xor a_inv(32) xor b_in(32);
carry_64 := result_with_carry(64);
if e_in.insn_type = OP_ADD then
    if e_in.output_carry = '1' then
       set_carry(v.e, carry_32, carry_64);
    end if;
    if e_in.oe = '1' then
        set_ov(v.e,
               calc_ov(a_inv(63), b_in(63), carry_64, result_with_carry(63)),
               calc_ov(a_inv(31), b_in(31), carry_32, result_with_carry(31)));
    end if;

-- 
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 319] POWER9 setting carry (and other) XER flags
From: bugzilla-daemon @ 2020-05-20  4:50 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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> michael could you convert all the outgoing XER fields to a Data record type?

done, it needs checking.

also, the CR pipeline needs likewise converting so that CROutputData.cr is of
type Data.

then, the op.input_cr and op.output_cr fields i believe are involved.
op.output_cr should be set to CROutputData.cr.ok to indicate "this instruction
outputs a CR register"

-- 
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 184] new mailing lists proposal for libre-soc.org
From: bugzilla-daemon @ 2020-05-20  5:58 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>

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

--- Comment #16 from Jacob Lifshay <programmerjake@gmail.com> ---
don't know that this is the right bug report:

the CI build status mailing list and the sendmail bash script and the calling
gitlab-ci-archiver all need to be set up -- gitlab-ci-archiver will probably be
running on jacob-build-server.

the gitlab rust library that's used needs to have the changes upstreamed which
is mostly stalled, additionally, the upstream is currently rewriting the API in
a different way than how I had written the API modifications that
gitlab-ci-archiver is relying on.

The pull requests for my modifications:
https://gitlab.kitware.com/utils/rust-gitlab/-/merge_requests/215
https://gitlab.kitware.com/utils/rust-gitlab/-/merge_requests/217

The upstream changelog for the upstream API modifications:
https://gitlab.kitware.com/utils/rust-gitlab/-/blob/master/CHANGELOG.md#new-api-strategy

-- 
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 328] New: move decoder RB exts function into nmutil
From: bugzilla-daemon @ 2020-05-20  6:06 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 328
           Summary: move decoder RB exts function into nmutil
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/power_decoder2.py;h=862c5ea3e72c138edbe19f5b1a937238e35883ad;hb=HEAD

exts is really useful and code duplication occurs in alu main_pipe OP_EXTS.

creating nmutil/exts.py would help avoid duplication

-- 
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 328] move decoder RB exts function into nmutil
From: bugzilla-daemon @ 2020-05-20  6:06 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-328-13@https.bugs.libre-soc.org/>

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

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 305] Create Pipelined ALU similar to alu_hier.py
From: bugzilla-daemon @ 2020-05-20  6:06 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=328

-- 
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 19may2020
From: Tobias Platen @ 2020-05-20  6:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDwRS5yHWa=qnyZhCe5tux6Q=9KiXvxg5M_x21=GZ5tnaw@mail.gmail.com>

On Tue, 19 May 2020 I was re-reading 'ScoreBoard Mechanics1.pdf' and 'ScoreBoard Mechanics2.pdf'.

_______________________________________________
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