IRTools.jl
glow
| IRTools.jl | glow | |
|---|---|---|
| 2 | 6 | |
| 107 | 3,151 | |
| 0.9% | 1.0% | |
| 5.4 | 8.2 | |
| 7 days ago | 3 days ago | |
| Julia | C++ | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
IRTools.jl
- From Julia to Rust
-
Ask HN: Show me your Half Baked project
Which is the concept behind Cassette.jl (https://github.com/jrevels/Cassette.jl) and IRTools.jl (https://github.com/MikeInnes/IRTools.jl).
glow
-
Accelerating AI inference?
Pytorch supports other kinds of accelerators (e.g. FPGA, and https://github.com/pytorch/glow), but unless you want to become a ML systems engineer and have money and time to throw away, or a business case to fund it, it is not worth it. In general, both pytorch and tensorflow have hardware abstractions that will compile down to device code. (XLA, https://github.com/pytorch/xla, https://github.com/pytorch/glow). TPUs and GPUs have very different strengths; so getting top performance requires a lot of manual optimizations. Considering the the cost of training LLM, it is time well spent.
-
Decompiling x86 Deep Neural Network Executables
It's pretty clear its referring to the output of Apache TVM and Meta's Glow
-
US government bans export of NVIDIA A100 to China and Russia, effective immediately
I also disagree with this. For example, Meta seems desperate about AI accelerators, and in fact is already doing "hardware customers develop software stack themselves" I mentioned above: Glow is that stack. Meta is doing Glow even if there is no promising AI accelerators right now, they are that desperate.
-
If data science uses a lot of computational power, then why is python the most used programming language?
For reference: In Tensorflow and JAX, for example, the tensor gets compiled to the intermediate XLA format (https://www.tensorflow.org/xla), then passed to the XLA complier (https://github.com/tensorflow/tensorflow/tree/master/tensorflow/compiler/xla/service) or the new TFRT runtime (https://github.com/tensorflow/runtime/blob/master/documents/tfrt_host_runtime_design.md), or some more esoteric hardware (https://github.com/pytorch/glow).
-
Esperanto Champions the Efficiency of Its 1,092-Core RISC-V Chip
The main reasons are hiring, and depth and breadth of the product.
Compilers are hard, device support is hard, the compiler community is small and closed source compilers quickly become weird tech islands.
https://github.com/pytorch/glow
- From Julia to Rust
What are some alternatives?
JET.jl - An experimental code analyzer for Julia. No need for additional type annotations.
tvm - Open deep learning compiler stack for cpu, gpu and specialized accelerators
Dagger.jl - A framework for out-of-core and parallel execution
serving - A flexible, high-performance serving system for machine learning models
Juleps - Julia Enhancement Proposals
XLA.jl - Julia on TPUs
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
StaticArrays.jl - Statically sized arrays for Julia
egg - egg is a flexible, high-performance e-graph library
Symbolics.jl - Symbolic programming for the next generation of numerical software
runtime - A performant and modular runtime for TensorFlow