| 26 May 2025 |
 @trofi:matrix.org | gcc does not require copyright assignment: https://gcc.gnu.org/dco.html | 12:49:35 |
 Tristan Ross | In reply to @emilazy:matrix.org
(not sure why we are doing more calls after everyone else on the team said it's not a good fit…) I know not everyone is available for calls which is why I made a doc. I think a mixture of async + sync is good. We can all be on the same page with the design doc while some of us are doing a call to pair up and blaze through things. | 20:42:22 |
| Tristan Ross | In reply to @trofi:matrix.org
Split GCC up similar to LLVM to accomplish this
I would suggest getting llvm-only bootstrap on linux first :)
An LLVM only bootstrap would take a lot of work that I'd be comfortable with after we have toolchain attrs | 20:50:44 |
| Tristan Ross | It would certainly be easier | 20:51:34 |
 John Ericson | Unless we drop GCC although, I think the GCC split up is something we need to do either way | 20:55:01 |
| Tristan Ross | Yeah, but I don't think we can drop GCC. | 21:04:07 |
| Tristan Ross | I consider it part of the "defacto standard Linux environment" | 21:04:27 |
 Grimmauld (any/all) | tbf, fhs-compliance is also part of the de-facto standard... | 21:04:57 |
| Tristan Ross | Kinda like GNU coreutils | 21:05:01 |
| Grimmauld (any/all) | nothing that can't be fixed given enough patches | 21:05:08 |
| Tristan Ross | In reply to @grimmauld:grapevine.grimmauld.de
tbf, fhs-compliance is also part of the de-facto standard... Well, we're exempt from that | 21:05:13 |
| Grimmauld (any/all) | i quite enjoy building the same thing with different toolchains - it shows where the flaky parts are, where assumptions are being made that might not hold | 21:06:11 |
| Grimmauld (any/all) | not having gcc would be fancy. | 21:06:24 |
| @trofi:matrix.org | would be nice not to have a cross-only llvm | 21:06:41 |
| @trofi:matrix.org | but having an llvm-only bootstrap would be a good test if it's easy to make a componentized-gcc bootstrap | 21:07:09 |
| @trofi:matrix.org | (i think it's very much not easy, but you already know that) | 21:07:33 |
| Tristan Ross | Yeah | 21:08:44 |
| Tristan Ross | I've already been looking into things to make it possible | 21:08:54 |
| Tristan Ross | One of the reasons why I've been working on fixing up pkgsLLVM | 21:09:11 |
| Tristan Ross | More things that work there, the better they'll work natively | 21:09:24 |
| Tristan Ross | Plus, I'll run native LLVM once it's possible | 21:09:35 |
| Tristan Ross | Rebuild the world on Ampere with 128 cores. | 21:09:50 |
| Grimmauld (any/all) | before i do that i want proper tooling to not do world rebuilds whenever i poke at some low-level dep... | 21:10:30 |
| Grimmauld (any/all) | i suppose thatn is on nix, not stdenv... | 21:10:45 |
| @trofi:matrix.org | Yeah, nix does not give you an easy way to graft a low-level dependency. | 21:11:48 |
 emily | In reply to @rosscomputerguy:matrix.org
I know not everyone is available for calls which is why I made a doc. I think a mixture of async + sync is good. We can all be on the same page with the design doc while some of us are doing a call to pair up and blaze through things. I'm not sure how we're meant to work together as a team when IIRC every single other member present agreed that sync calls don't suit their availability... if the vast majority of the team can't make the calls then we can't make collective decisions on them as a team, so either it won't actually be able to move design/decisions forward or it'll just be pushing things through without consensus. | 21:22:01 |
| emily | even if we had the collective availability for it it's very hard to schedule sync calls across a distributed international team on a regular basis unless there's consistent availability at specific times | 21:22:45 |
| emily | which is not really realistic when we are all working as volunteers and have communicated the constraints on our time and how we can best collaborate effectively under them... | 21:23:15 |
| Tristan Ross | I understand that part, at least Ericson and I are able to work together on pairing up together and we can work async with the rest of the team. | 21:24:50 |
| Tristan Ross | Ericson and I are going to work on some libc improvements soon. After I come back from Florida, I'll be splitting GCC up. | 21:26:39 |
