4 ms·
You may want to clarify that in the GitHub repo, too. See my issue there. If you want to go the didactic route, then consider documenting the improvements over
by mikemike 4y ago
You may want to clarify that in the GitHub repo, too. See my issue there.
If you want to go the didactic route, then consider documenting the improvements over the naive implementation: register hinting, register priorities (PHI), two-headed register picking, fixed register picking, optimized register picking for 2-operand instructions (x86/x64), register pair picking, ABI calling-conventions, weak allocations, cost heuristics, eviction heuristics, lazy/eager spill/restore, rematerialization, register shuffling (PHI) with cycle breaking, register renaming, etc. That's all in ~2000 lines of lj_asm.c.
- mkeeter 4y agoDone, I've added the same disclaimer to the Github repo. Given that your Github issue [1] was originally titled "Take Down Notice", I'm now hesitant to read any LuaJIT code. If I read lj_asm.c and learn from it, will you try to take down any register allocation code that I write in the future? [1] https://github.com/mkeeter/ssra/issues/1 https://github.com/mkeeter/ssra/issues/1
- mikemike 4y agoI had already changed the title after your reply. The objection is about the naming, which implies an invention claim without further explanation. It's not about the code.
- fros1y 4y agoWait, Are you demanding that independent implementations of an idea you explicitly dedicated to the public domain must then describe the various ways your version is “superior”? Who hurt you?