7 ms·

https://github.com/intel/llvm https://github.com/intel/llvm https://github.com/iree-org/llvm-project https://github.com/iree-org/llvm-project https://github.c

https://github.com/intel/llvm https://github.com/intel/llvm https://github.com/iree-org/llvm-project https://github.com/iree-org/llvm-project https://github.com/ROCm/llvm-project https://github.com/ROCm/llvm-project https://github.com/apple/swift-llvm https://github.com/apple/swift-llvm https://github.com/dotnet/llvm-project https://github.com/dotnet/llvm-project https://github.com/espressif/llvm-project https://github.com/espressif/llvm-project should i keep going?

anttiharju 1y ago
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 1y ago
  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 1y ago
    Fork without context usually means a hard fork.
    - almostgotcaught 1y ago
      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.
  - deleted 1y ago
    [deleted]
Kranar 1y ago
Three of those are forks to upstream back to the main repo, and one of them is dead.
- almostgotcaught 1y ago
  > 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
debugnik 1y ago
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.

anttiharju 1y ago

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 1y ago
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 1y ago
  Fork without context usually means a hard fork.
  - almostgotcaught 1y ago
    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.
- deleted 1y ago
  [deleted]

Kranar 1y ago

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

almostgotcaught 1y ago
> 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

debugnik 1y ago

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.