-
Updated
Jul 9, 2022 - WebAssembly
compilers
Here are 859 public repositories matching this topic...
-
Updated
Jul 9, 2022
-
Updated
Jul 3, 2022 - C++
-
Updated
Feb 1, 2022
-
Updated
Jun 29, 2022 - C
-
Updated
Mar 28, 2022 - Python
-
Updated
Feb 27, 2022 - JavaScript
-
Updated
May 15, 2020 - Rust
-
Updated
May 16, 2022 - C
-
Updated
Jun 24, 2022
-
Updated
Jul 8, 2022 - Python
-
Updated
Aug 8, 2019 - C
-
Updated
Jan 18, 2021 - C++
-
Updated
Aug 23, 2021 - C
-
Updated
Feb 4, 2022 - OCaml
-
Updated
Oct 23, 2016 - C++
-
Updated
Jul 5, 2022 - Jupyter Notebook
-
Updated
Oct 28, 2019 - Ruby
The current runtime source generates a lot of warnings when being compiled. We should go through and fix the ones we can and suppress the ones we think are OK.
-
Updated
Jul 6, 2022 - WebAssembly
-
Updated
Apr 9, 2019 - Racket
-
Updated
Feb 24, 2020 - Haskell
-
Updated
Apr 17, 2022 - Go
Improve this page
Add a description, image, and links to the compilers topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the compilers topic, visit your repo's landing page and select "manage topics."

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

EH1 has a lot of examples where a sequent CFunc contains only a handful ot statements (often 1 or 2) and is called only once. This causes a performance penalty when --output-split puts these in a different function than _eval and hence the compiler can't inline them, so we should inline these ourselve when it's obviously the right thing to do.