4 ms·
This is a non-issue. YJIT only targets x86-64. After all, this is a JIT. If you designed a new architecture X, you need to port YJIT itself to target X, in addi
by sanxiyn 5y ago
This is a non-issue. YJIT only targets x86-64. After all, this is a JIT. If you designed a new architecture X, you need to port YJIT itself to target X, in addition to GCC, LLVM, etc.
- throwaway-m3232 5y agoOh, so YJIT is highly coupled to x86-64? Porting GCC + yjit is less work than porting GCC + yjit + LLVM.
- FooBarWidget 5y agoIt's not like new architectures appear very quickly, much less adopted very quickly. The benefits of maintenance overhead reduction and development speed increase, far outweight the theoretical downside of having to port LLVM to that new architecture.
- byroot 5y agoIt’s not that it’s highly coupled, just that it’s still the early days and only x86_64 was on the roadmap. Arm64 is planned, and will hopefully make it into Ruby 3.2
- FullyFunctional 5y agoAnd with an Arm64 backend, adding RISC-V is probably going to be a walk in the park.
- lalaithion 5y agoWhy even port GCC at all, and not simply LLVM?
- lnxg33k1 5y agoBut why not just buy an existing CPU on amazon
- dkersten 5y agoSo just port LLVM + yjit.