llvm-project

They are there: cplusplus_top_200.csv:llvm-project,https://github.com/llvm/llvm-project,C++,48,0,2573,5,652.3,2... c_top_200.csv:postgres,https://github.com/postgres/postgres,C,124,0,50,5,41.1,52,1,... sqlite sorry since it is not hosted on github, and we do plan to add non-github repos in future.

I was curious about the gcc blocker. It mostly seems to be due to formulae that depend on GNU Fortran. However, there's a Fortran front-end for LLVM: https://github.com/flang-compiler/flang/wiki https://github.com/llvm/llvm-project/tree/master/flang/ I wonder if it's an alternative to waiting on gcc gaining arm64 support. Frankly, I don't see why any of homebrew should have to depend on gcc.

You may also want to try the GN build: https://github.com/llvm/llvm-project/blob/master/llvm/utils/...

I think while flang (https://github.com/llvm/llvm-project/tree/master/flang) is getting more stable. It would be a lot easier to compile Fortran into WASM with LLVM's WASM backend

The f18 Fortran compiler has a novel algorithm (calculating in base 10^16) for conversions that is fast and doesn't require big look-up tables. https://github.com/llvm/llvm-project/tree/master/flang/lib/D...

The new URL is a nice overview but doesn't mention at which commit the code got merged: https://github.com/llvm/llvm-project/commit/94faadaca4e1704f...

Apple’s strange ABI is upstreamed: https://github.com/llvm/llvm-project/search?q=arm64_32&unsco.... Not sure what “column” you’re talking about, but it’s fairly clear that macOS’s clang is based on a fairly recent LLVM that they branched off of (you can even grab the underlying version number if you know where to look). And profiles for Apple silicon chips are readily available: https://github.com/llvm/llvm-project/blob/954db63cd149df031d.... LLVM is probably one of the projects from Apple that sees the most things get upstreamed.

For compiler-rt it is Apache 2.0 license https://github.com/llvm/llvm-project/blob/master/compiler-rt...

This is incorrect, the LLVM project has an official Fortran compiler in tree called flang: https://github.com/llvm/llvm-project/tree/master/flang It is quite hard to write portable Fortran code, but code that at least compiles with PGI should compile with that as well.

Is this related to flang? https://github.com/llvm/llvm-project/tree/master/flang/

> OrcJIT has a pretty decent caching layer (Sadly) this is not correct. If you want to cache compiled code between sessions, your only option so far are handwritten object caches along the lines of this example: https://github.com/llvm/llvm-project/blob/ae47d158a096abad43...

From a very quick search I can't seem to find such a branch. Judging from https://github.com/llvm/llvm-project/releases they seem to occasionally branch release candidate branches from master, every two weeks or so. That's very far from a well-tested master updated several times a day. Continuous integration for compilers is a well-understood problem. There are posts in this thread explaining how Rust handles it. I understand that it's a royal pain to set up and maintain. I am a compiler engineer and am happy to work on compilation stuff but wouldn't want to touch our CI system with a ten-foot pole. But LLVM is a project driven by Google and Apple, there are really no excuses for not finding the people willing to do this.

There is a fallacy in taking enterprises that might be done "eventually" as being already completed and ultimately proven. What you quote is not disagreeing with what I was saying at all. Quick look at the GCC link you posted: Project Status (last updated 06/2009) Phase 1 of gcc-in-cxx now complete (06/2009) gcc-in-cxx completes bootstrap as of 03/2009 Seriously. > "Provide C symbols as specified by the standards, but take advantage and use C++ language facilities for the core implementation." Sure, now let's look at the code https://github.com/llvm/llvm-project/blob/master/libc/src/ Oh, it's not even a completed project. Here is stdio https://github.com/llvm/llvm-project/blob/master/libc/src/st... stdio/ for example has just 3, mostly empty files: file.h, fwrite.cpp, fwrite.h. Last commit was 8 days ago. It's not a p