01:29:44 <jbk> hrm.. i don't know if anyone knows offhand if there's a way in node.js to distinguish between solaris and illumos without having to run and parse the output of uname -o ?
01:51:10 <gemelen> jbk: os.version() is likely to be distinct
01:53:56 <gemelen> (even if it's just an easier way to do the same as you've suggested)
12:35:24 <Dixie_F> Successfully using the latest LLMs for code generation seems to me to hinge upon breaking up tasks into pieces that are clearly defined.  Using something for project management (beads) can help.  Tell LLM to create a detailed plan for conversion that breaks it up into manageable pieces.  Then assign or auto assign various agents to each of the tasks.  In my experience, the problems come when the planning and ex
12:35:24 <Dixie_F> ecution are mixed.  Without specific instructions for a manageable duration task, the goals seem to get lost in the growing context.  The latest LLMs are shockingly consistent at completing small tasks (although typos do creep in).  Codex rebooted my smartos box due to a quoting error while searching a log for "reboot."
15:50:39 <extrowerk> Dixie_F: :D
21:28:20 <richlowe> b.exp
21:28:29 <richlowe> oops
22:34:18 <richlowe> gwr: circumstantial evidence from aarch64 automated tests: the libc symbol tests are half of my runtime for the (non-filesystem) test suites
22:34:28 <richlowe> and there's one fewer ISA on aarch64
22:34:36 <richlowe> so I imagine your header-test thing will make a bunch of people happy :)
23:08:00 <gwr> What do the make variables ARCH and ARCH64 expand to on ARM64?
23:08:30 <richlowe> both expand to aarch64 for unfortunate reasons
23:08:43 <richlowe> but uses are guarded based on whether the platform is multilib or not
23:08:47 <gwr> I'd like to figure out at build time if the target for which we're creating things does 64-bit, 32-bit or both.
23:09:05 <richlowe> gwr: I just put up a huge fucking ugly PR to the arm64-gate for that
23:09:24 <richlowe> I designed it not to be clean, but to merge easily for me
23:10:13 <richlowe> if I were doing it properly, I'd probably do the `$(MACH)/Makefile`, `../Makefile.com` dance, but I converted one suite to that and did some experimental merging and it was not going to fly 
23:11:01 <richlowe> the gist of it is ISA-d binaries land in 32/ and 64/ directories, so we can guard one against i86pc in the runfiles
23:11:16 <richlowe> and still uses test groups
23:11:28 <richlowe> (that is, the directories only exist to pacify test-runner)
23:13:13 <richlowe> I think the other thing to know is that for obvious reasons arm64-gate has a `$(BUILD32)` (cf. $(BUILD64))