Would be great to see any confirmation.

almostgotcaught · 2025-10-04T05:26:48 1759555608

should i keep going?

debugnik · 2025-10-04T07:44:50 1759563890

You should have ordered them differently to not distract from your point: That most LLVM-based compilers do eventually need to write patches for it and usually ship them before upstreaming, they can't just use an existing release. I at least have always found that to be true to build such compilers from source.

Kranar · 2025-10-04T06:03:03 1759557783

Three of those are forks to upstream back to the main repo, and one of them is dead.

almostgotcaught · 2025-10-04T06:15:06 1759558506

> Three of those are forks to upstream back to the main repo

and you think the patches they upstream they don't use in the meantime...?

> and one of them is dead.

yes because the currently used fork isn't public obviously

anttiharju · 2025-10-04T05:55:12 1759557312

Checking the first one

> Intel staging area for llvm.org contribution. Home for Intel LLVM-based projects.

Seems like they use it to contribute to upstream which is business as usual?

almostgotcaught · 2025-10-04T06:16:37 1759558597

what exactly do you people think a fork is? hint: it's not a complete forever and ever and ever divergence.

Edit: the concept of fork and hard fork are distinct. I specifically used the word fork

IshKebab · 2025-10-04T07:13:32 1759562012

Fork without context usually means a hard fork.

almostgotcaught · 2025-10-04T18:56:31 1759604191

Oh interesting I didn't realize the role of adjectives has changed recently. So war and my nuclear war mean the opposite things now. I'll keep that in mind.