lkcl | mikolajw: this means you haven't run the dev-env-setup script | 10:40 |
---|---|---|
lkcl | https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=hdl-dev-repos;h=d1751d2f68516575ab191c743b69635b053e47e0;hb=51bc9c3ad8838c86db53ed21b95c3b8c154ff22b#l41 | 10:40 |
lkcl | ah, yep, found a spelling error (on a command that is never used because it's run from a different location) | 10:41 |
lkcl | generally we don't run "make test" unless having about 2 days spare to wait for it to complete | 10:43 |
lkcl | yep, that's out-of-date, i moved power_decoder.py to openpower-isa several months ago | 10:44 |
lkcl | therefore it does nothing | 10:44 |
lkcl | i've removed svanalysis from the soc Makefile because it's part of openpower-isa (moved several months ago) | 10:53 |
lkcl | added a page with links to nmigen tutorials | 11:00 |
lkcl | https://libre-soc.org/docs/learning_nmigen/?updated | 11:00 |
ghostmansd-pc | lkcl: shouldn't we also add XLEN to parser? | 17:15 |
ghostmansd-pc | I see that you updated ISACaller namespace with XLEN=64, but, since the whole pseudocode is parsed before ISACaller enters the scene, we should teach parser and lexer XLEN, shouldn't we? | 17:17 |
veera[m] | Hi | 17:17 |
veera[m] | Hi lkcl | 17:17 |
veera[m] | lkcl: Did RFP mail reached you? | 17:25 |
lkcl | ghostmansd-pc, it's treated as simply "yet another variable" | 18:46 |
lkcl | so, no | 18:46 |
lkcl | veera[m]: yes.... i spam | 18:47 |
lkcl | veera[m], you need to adjust the Phase/Milestones | 18:48 |
lkcl | you have the old field :Phase/milestone(s): 384 389 626 634 651 | 18:48 |
lkcl | that needs to be changed to: 626 634 651 | 18:48 |
lkcl | oh ok you have 2 extra ones, 384 and 389 - take those out | 18:48 |
ghostmansd | lkcl: already found it, thanks | 18:49 |
ghostmansd | lkcl: let's spam in two places simultaneously :-D | 18:49 |
lkcl | ghostmansd :) | 18:50 |
lkcl | veera[m], everything else looks good | 18:50 |
lkcl | send it to the same 2 email addresses as last time | 18:50 |
ghostmansd | lkcl: I _think_ that minus sign should not be part of number token | 18:50 |
ghostmansd | I suspect should be handled at parser level | 18:51 |
ghostmansd | i.e. the parser should differ (a - b) and (-b), based on context. In fact, if I drop the sign from regex, it looks like it already does. I haven't tried any complicated cases, though. | 18:52 |
ghostmansd | let me try something like XLEN - -1 | 18:53 |
ghostmansd-pc | FWIW, since recent I see a lot of warnings from power_decoder.py, about unused PowerDecoder object. Is it a known issue, or maybe this is not an issue at all? | 19:25 |
lkcl | yeh ignore it | 19:28 |
lkcl | the reason is, you're supposed to use nmigen objects in a module | 19:28 |
lkcl | and one of the very common mistakes in nmigen HDL is to instantiate an object but not actually link it to anything | 19:29 |
lkcl | so whitequark added a check "is this nmigen object actually used, if no produce a warning" | 19:29 |
lkcl | but we use nmigen objects in the *emulator*... without actually linking them to anything. | 19:29 |
lkcl | hence the warnings... which can be ignored | 19:30 |
mikolajw | does anyone have a suggestion what could be a good first contribution to the SoC itself? I need something simple and self-contained. I have no prior experience in Nmigen and SoC design | 20:22 |
ghostmansd-pc | lkcl: can we disable it e.g. via some environment variable? If test fails, these appear below the log. | 20:38 |
lkcl | mikolajw, can i suggest going through the "first steps" page that ghostmansd-pc wrote last week? | 20:41 |
lkcl | https://libre-soc.org/docs/firststeps/ | 20:42 |
lkcl | ghostmansd-pc, there is - i think - it's somewhere in nmigen source code | 20:43 |
lkcl | class Elaboratable... | 20:44 |
lkcl | class MustUse: | 20:46 |
lkcl | _MustUse__silence = False | 20:46 |
lkcl | in nmigen._unused.py | 20:46 |
lkcl | so you can monkey-patch nmigen._unused.MustUse and set _MustUse__silence=True | 20:48 |
lkcl | ghostmansd-pc, yyeahh i was just experimenting with that MINUS comparison and yeah it seems to work | 21:05 |
ghostmansd | Yep, though I'm still far from understanding what it has to do with comparisons. | 21:10 |
lkcl | it's just a moniker | 21:17 |
lkcl | BNFs are often full of things that have the wrong name, esp. if they're hacked together | 21:17 |
lkcl | or, as is most likely in this case, two BNFs were merged into one, from a formerly "good" BNF that had too many features to implement in a simple example | 21:18 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!