| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has quit IRC | 05:04 | |
| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has joined #libre-soc | 05:16 | |
| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has quit IRC | 06:13 | |
| *** lxo <lxo!~lxo@gateway/tor-sasl/lxo> has joined #libre-soc | 06:14 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-109-173-83-100.ip.moscow.rt.ru> has quit IRC | 08:21 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.41.208> has joined #libre-soc | 08:22 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.41.208> has quit IRC | 08:29 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.162.76> has joined #libre-soc | 08:38 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.162.76> has quit IRC | 09:17 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-109-173-83-100.ip.moscow.rt.ru> has joined #libre-soc | 09:18 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-109-173-83-100.ip.moscow.rt.ru> has quit IRC | 09:37 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.55.60> has joined #libre-soc | 09:38 | |
| ghostmansd[m] | lkcl, I just recalled that we still haven't discussed if another task which causes less conflicts and debates is available. :-) | 09:58 |
|---|---|---|
| ghostmansd[m] | https://libre-soc.org/irclog/%23libre-soc.2023-05-18.log.html#t2023-05-18T19:12:43 | 09:59 |
| ghostmansd[m] | BTW, searching in IRC logs yields 404: https://libre-soc.org/irclog/search?q=anything | 10:00 |
| lkcl | i know i haven't added the cgi-script | 11:34 |
| lkcl | the model simulator is a really high business priority and i do not have the time to take on that task as well | 11:35 |
| lkcl | i am dealing with the specification which is extremely complex and taking all of my energy and focus | 11:35 |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.55.60> has quit IRC | 11:36 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.55.60> has joined #libre-soc | 11:36 | |
| lkcl | i know what is happening with the model: it's not yet at the point where iterative feedback is possible, so there is "nothing to understand, no context, nothing" | 11:37 |
| lkcl | once it produces actual output based on input then understanding will follow and it takes off from there | 11:38 |
| ghostmansd[m] | I need some task which has some space for manoeuvre and free will. | 12:04 |
| ghostmansd[m] | Considering the overall feedback, I really don't want to handle this task, _especially_ if this is high priority. | 12:06 |
| lkcl | there's two high-priority tasks: i am tackling the spec feedback and communication with the OPF ISA WG | 12:07 |
| lkcl | i cannot do both | 12:07 |
| lkcl | the model is a very simple task | 12:07 |
| lkcl | far simpler than imagined | 12:07 |
| lkcl | there are no external imports - not one single one - bar absolute basic imports and certainly absolutely nothing from any of our repos. | 12:08 |
| lkcl | its only input is an ASCII file in a well-defined format | 12:08 |
| lkcl | its only output is an ASCII file in a markdown-table format | 12:08 |
| ghostmansd[m] | "a very simple task" — not if any solution goes under heavy criticism and is later totally refactored according to personal preferences. | 12:09 |
| ghostmansd[m] | If this is a high-priority task, then you should either relax the requirements or pass it to someone else. I also have a personal situation here and go through quite complicated stuff right now, and I don't want to waste my time and energy on debates and looking at the code which was shitty according to someone else's standards. It's fine per se to have different opinions, but if somebody writes a totally different code than you expect than perhap | 12:14 |
| ghostmansd[m] | the wrong person to implement the functionality is chosen. | 12:14 |
| lkcl | they're not "personal preferences", there are specific reasons for keeping it short and brutally simple | 12:17 |
| lkcl | i may have to actually present this code directly to customers | 12:17 |
| lkcl | as part of a presentation | 12:17 |
| lkcl | if it has complex classes that span multiple pages, i cannot put those onto a slide | 12:17 |
| lkcl | if it has concepts that are not easy to read by a non-expert python programmer, i cannot explain them in a reasonable amount of time | 12:18 |
| lkcl | so the code has to be written in a style that an (intelligent) beginner of only 6-months programming experience can easily grasp | 12:20 |
| ghostmansd[m] | Why should you post code? You should post the principle and the algorithm, not implementation details. | 12:20 |
| lkcl | because this is very much like a "config file" | 12:20 |
| lkcl | where the pipeline lengths will be parameters that can be changed by the customer, to experiment | 12:21 |
| lkcl | it also means plenty of explanatory code-comments are needed | 12:21 |
| lkcl | it's a very different style from one where an advanced programmer would create classes, dataclasses, use regex's because they cope with complex data patterns and so on | 12:22 |
| lkcl | ok i'm done with shift-and-add https://bugs.libre-soc.org/show_bug.cgi?id=1091 | 12:53 |
| lkcl | i'm still doing a spec-change from the new LD/ST-Indexed format | 12:54 |
| lkcl | ghostmansd[m], actually, could you do that? | 12:55 |
| ghostmansd[m] | Update the spec? What's the repo, libreriscv? | 13:05 |
| ghostmansd[m] | Also binutils must be updated too. :-) | 13:05 |
| ghostmansd[m] | Hm, I suspect there already is SH field, isn't it? | 13:06 |
| ghostmansd[m] | If these occupy different bits, this might cause it to be renamed in binutils. | 13:06 |
| ghostmansd[m] | Paul suggested SHM1 | 13:08 |
| lkcl | yes, i... sigh | 13:10 |
| lkcl | yes that's a real simple one to look at | 13:11 |
| lkcl | can you do it under #1091? | 13:11 |
| lkcl | it's something-to-do | 13:11 |
| lkcl | the LD-ST-Indexed thing is a little more involved, it's literally introducing a new EXTRA format that is a *mixed* EXTRA3-EXTRA3-EXTRA2 form | 13:12 |
| lkcl | by using bits 6&7 as MASK_SRC | 13:13 |
| lkcl | that involves quite a shuffle in power_insn.py (esp of the base classes) | 13:14 |
| ghostmansd[m] | I'll take a look at fields renaming, => SHM1, including binutils, np | 14:12 |
| ghostmansd[m] | And also 1079, later | 14:13 |
| lkcl | don't make it SHM1 - that's a misunderstanding by the IBM team. the name was suggested "Shift Minus 1" which is *not correct* | 15:21 |
| lkcl | SH1 would be fine because actually it really is SH+1 | 15:21 |
| lkcl | SHP1 would do but i am not keen on 4-character-long fields | 15:21 |
| lkcl | ya know what? screw it: SHP1 is pretty clear | 15:52 |
| lkcl | sigh you'll have to follow the action-log here to do the same thing, sigh https://bugs.libre-soc.org/show_bug.cgi?id=1091#c0 | 15:53 |
| ghostmansd[m] | np, I'll handle it :-) | 16:33 |
| ghostmansd[m] | Already checked the logs to realize that I have to repeat what's done already :-) | 16:34 |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@176.59.55.60> has quit IRC | 19:04 | |
| *** ghostmansd[m] <ghostmansd[m]!~ghostmans@broadband-109-173-83-100.ip.moscow.rt.ru> has joined #libre-soc | 19:06 | |
| *** markos_ <markos_!~markos_@user/markos/x-1838887> has quit IRC | 19:37 | |
| *** markos_ <markos_!~markos_@static062038151250.dsl.hol.gr> has joined #libre-soc | 19:51 | |
| *** markos_ <markos_!~markos_@user/markos/x-1838887> has joined #libre-soc | 19:51 | |
| lkcl | ghostmansd[m], well sigh if the name is better it has to be done, wark-wark | 20:29 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!