Llvm-project Alternatives

Similar projects and alternatives to llvm-project

julia

350 44,534 10.0 Julia llvm-project VS julia

The Julia Programming Language
Pytorch

340 78,016 10.0 Python llvm-project VS Pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
parca

18 3,848 9.9 TypeScript llvm-project VS parca

Continuous profiling for analysis of CPU and memory usage, down to the line number and throughout time. Saving infrastructure cost, improving performance, and increasing reliability.
Pkg.jl

5 603 9.0 Julia llvm-project VS Pkg.jl

Pkg - Package manager for the Julia programming language
PlotDocs.jl

3 92 2.4 llvm-project VS PlotDocs.jl

Documentation for Plots.jl
parca-demo

2 10 4.7 HTML llvm-project VS parca-demo

A collection of languages and frameworks profiled by Parca and Parca agent
CondaPkg.jl

1 111 6.3 Julia llvm-project VS CondaPkg.jl

Add Conda dependencies to your Julia project
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better llvm-project alternative or higher similarity.

Suggest an alternative to llvm-project

llvm-project reviews and mentions

Posts with mentions or reviews of llvm-project. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-10.

Julia 1.9 Highlights
9 projects | news.ycombinator.com | 10 May 2023

I'm not aware of bugs with offset arrays in the standard library. It's happened before and it may happen again, but Base and the standard library are generally very good at avoiding that.
The main problem is non-standard library packages that were written back in early julia days before OffsetArrays existed (e.g. a big offendeder IIRC was StatsBase.jl), and so wasn't written with any awareness of how to deal with generic indexing.
OffsetArrays.jl are a neat trick, and sometimes they really are useful e.g. when mimicing some code that was written in a 0-based language, or just when you're working with array offsets a lot, but I wouldn't really recommend using them everywhere. Other non-array indexable types like Tuple don't have 0-based counterparts (as far as I'm aware), so you'll be jumping back and forth from 0-based and 1-based still, and it's just an extra layer of mental load.
Honestly though, it's often not very necessary to talk about array indices at all. The preferred pattern is just to use `for i in eachindex(A)`, `A[begin]`, `A[end]` etc.
> and IIRC also the language build depends on a fork of LLVM (https://github.com/JuliaLang/llvm-project)
Yes, we use a fork of LLVM, but not because we're really changing it's functionality, just because we have patches for bugs. The bugs are typically reported upstream and our patches are contributed, but the feedback loop is slow enough that it's easiest to just maintain our own patched fork. We do keep it updated though (this release brings us up to v14) and there shouldn't be any divergences from upsteam other than the bugfixes as far as I'm aware