| lkcl | Guest55_, hii again mepy :) thanks for sending that message to the list the other day. | 13:44 |
|---|---|---|
| lkcl | toshywoshy, thank you for yesterday. i need to do a write-up for you about the test API. kylel helped write it, and will be documenting it. | 13:45 |
| lkcl | one "ooooOoo" moment i didn't raise yesterday: the python-based unit tests could actually be *used* to generate c programs! | 13:45 |
| lkcl | conforming to the OpenPOWER Validation Test Suite | 13:45 |
| lkcl | so whilst there's one option to run them directly (by gdbmi "remote" gdb single-stepping, which will be horribly slow) | 13:46 |
| lkcl | the other option is to use some sort of mixed c/assembler templating where the exact same unit test written into the openpower-isa test suites in python will *auto-generate* an *actual* c/assembler source code program | 13:47 |
| lkcl | where that program, when compiled and run, actually does the exact same job: runs the instruction and tests against the expected results | 13:48 |
| lkcl | kylel, if you'd be interested to do that, the idea was floated during the meeting to put in *another* NLnet Grant request, this time perhaps with some of the other OpenPOWER Foundation Members joining in | 13:49 |
| lkcl | (IBM, other) | 13:49 |
| kylel | That is an interesting idea | 14:38 |
| kylel | a heckuva lot more robust | 14:48 |
| kylel | Would be happy to assist | 15:05 |
| Guest55_ | lkcl thank you ! I quite always read – and try to understand – your emails! | 15:45 |
| lkcl | kylel, yeah it's just "yet another of the possibilities" | 16:02 |
| lkcl | and makes the Test API a potential candidate for at the very least a de-facto standard "you're on your own, it does the job, but it's your responsibility to check" OpenPOWER Compliance Test Suite | 16:03 |
| lkcl | i can't quite believe how little public cooperation there is right now on this. from 20+ years of Libre/Open development it's really quite taking me aback that every single OpenPOWER Foundation Member Company basically duplicates and maintains their own personal Compliance Test Suite. | 16:04 |
| kylel | it is interesting because you start to wonder sometimes just what is "correct" sometimes with so many moving parts and so many different projects/organizations sort of doing their own thing. | 16:25 |
| programmerjake | lkcl, note that generating assembler to test native power instructions is exactly what I'm planning on doing for the python rewrite of power-instruction-analyzer | 19:38 |
| programmerjake | so, that overlaps quite a bit | 19:38 |
| lkcl | programmerjake, ah not quite. that's a dynamic task, that actively runs *from* python to execute assembler (after first compiling it to a binary) | 20:23 |
| lkcl | the above idea is a *static* task | 20:23 |
| lkcl | zero actual execution (well, maybe) | 20:23 |
| lkcl | where it pretty much literally takes the unit test case assembly listings, drops them into a .s file (or potentially an inline asm block inside a c source file) | 20:24 |
| lkcl | blats out a standard template Makefile | 20:24 |
| lkcl | blats out a c template which outputs the pre-run reg inputs, runs the .s file and picks up the regfile contents afterwards | 20:25 |
| lkcl | and errr that's it | 20:25 |
| lkcl | it becomes the user's responsibility to type "make" | 20:25 |
| lkcl | at which point they end up with a binary executable that *they* run | 20:26 |
| lkcl | and it reports "OK" or "fail" as appropriate | 20:26 |
| lkcl | exactly like riscv-isa-tests does right now | 20:26 |
| lkcl | more sophisticated versions of that would output *different* templates | 20:26 |
| lkcl | (exactly like riscv-isa-tests does right now) | 20:27 |
| lkcl | one of those templates would be "physical bare metal machine" | 20:27 |
| lkcl | another would be "Virtual Memory is initialised before running the test" | 20:27 |
| lkcl | and so on and so forth | 20:27 |
| lkcl | all of which is completely different from *dynamically* - and from *python* - actually *executing* compiled assembler | 20:28 |
| programmerjake | ah, ok. so they could possibly share code | 20:56 |
| Las[m]_ | Is there any plan to migrate away from alliance for the soclayout stuff? | 21:35 |
| *** Las[m]_ is now known as Las[m]__ | 21:39 | |
| *** Las[m]__ is now known as Las[m]_ | 21:39 | |
| *** Las[m]_ is now known as Las[m] | 21:39 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!