| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has quit IRC | 05:41 | |
| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has joined #libre-soc | 05:42 | |
| ghostmansd[m] | lkcl, I recall you mentioned we could dedicate some grant from cavatools. Since these recent works relate to each and every subsystem which deals with instructions — pysvp64asm, pysvp64dis, potentially nmigen-related chunks, and sv_binutils, — it'd be really great. | 07:29 |
|---|---|---|
| *** ghostmansd <ghostmansd!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC | 08:28 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-188-32-220-156.ip.moscow.rt.ru> has quit IRC | 09:01 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.166.57> has joined #libre-soc | 09:02 | |
| lkcl | ghostmansd[m], yes absolutely. basically (deep breath) the plan is to do a nmigen-to-c compiler and a pseudocode-to-c compiler then cobble things together | 10:29 |
| ghostmansd[m] | Wow, sounds like a big project. | 10:30 |
| lkcl | not really. the first nmigen-to-c experiment took about... 3 weeks i think? it's already faster than the standard nmigen-python simulator and that's with the main loop still in nmigen using cffi | 10:34 |
| lkcl | and i'd expect the pseudocode-to-c compiler to be... mmm... a month? first version in under a week, stabilised in 3 | 10:35 |
| lkcl | nmigen uses an absolutely tiny subset "programming" language. | 10:36 |
| lkcl | arithmetic | 10:36 |
| lkcl | if | 10:36 |
| lkcl | else | 10:36 |
| lkcl | assignment | 10:36 |
| lkcl | that's all there is to it. so it was remarkably easy/quick to create a compiler. | 10:37 |
| lkcl | and the pseudocode is remarkably similar to python, so much so that i only needed to take dabeaz's python-ply GardenSnake.py example, fix the lexer errors, and convert its lexer symbols. | 10:38 |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has joined #libre-soc | 10:42 | |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has quit IRC | 11:06 | |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has joined #libre-soc | 11:08 | |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has quit IRC | 11:34 | |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has joined #libre-soc | 11:41 | |
| *** ghostmansd <ghostmansd!~ghostmans@176.59.166.57> has quit IRC | 12:03 | |
| ghostmansd[m] | lkcl, got it | 12:26 |
| ghostmansd[m] | What'd be the right task and the right amount for the work already done? I'm still checking a case with pysvp64asm, but once it's handled I'd like to connect the completed works to some tasks or subtasks. | 12:29 |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.166.57> has quit IRC | 14:07 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.166.57> has joined #libre-soc | 14:08 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@91.205.170.135> has joined #libre-soc | 14:09 | |
| lkcl | ghostmansd[m], i'm going to need to stop doing everything else and look at that for about 2 clear days. | 14:49 |
| lkcl | 4-5 if i have to do the cavatools MoU | 14:50 |
| lkcl | but | 14:50 |
| lkcl | because the cavatools grant *has* been approved, any work done that gets allocated to tasks *will* be payable. | 14:51 |
| ghostmansd[m] | Perfect, thank you! Meanwhile I'll continue working on extending this. | 14:54 |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@91.205.170.135> has quit IRC | 17:59 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.43.192> has joined #libre-soc | 18:02 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.43.192> has quit IRC | 18:20 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@91.205.170.135> has joined #libre-soc | 18:21 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@91.205.170.135> has quit IRC | 19:40 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.43.108> has joined #libre-soc | 19:40 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!