[COMPILER REQUEST]: Numba

[Rupt]

Compiler name

Numba

Compiler version

0.58.0

Compiler language

Python

Compiler homepage

https://numba.pydata.org/

Motivation

Numba compiles Python with LLVM.

It is a convenient way to make a restricted Python subset run fast, since it both compiles functions with an optimizing compiler and generates Python language interfaces.

From the CE perspective, I see it fitting as a separate language from Python, in the sense that it just uses Python as an intelligent code generator.

I have sketched an implementation in #5592.

Questions:

• [ ] Is the appropriate to add to Compiler Explorer? Numba compilation is a feature I have wanted in the past, but I understand that other factors weigh into the decision.
• [ ] How should Numba be installed in https://github.com/compiler-explorer/infra? It only needs a Python (already there) and a virtual environment with a few pypi packages installed. This might share a resolution with #4122.
• [ ] What is the minimum viable product? Numba exposes from several levels of its compilation process (types, asm, llvm, cfg). #5592 only implements asm inspection so far, and borrows execution from the existing Python implementation. Numba also supports CUDA.

[mattgodbolt]

So to answer some of the questions:

• is it apporirate? Absolutely! As I said in the PR I've hacked sometihng similar before for my own needs
• How should it be installed? This is the biggest issue. I posted on the PR but it mostly means a whole new way of installing python and virtual environments that's currently incompatible with the way we do instlaations.
• MVP -> any assembly output for numba-jitted code :)

[Rupt]

So we have at least two potential users! Nice. I appreciate the positivity. Thank you for taking time to respond.

• How should it be installed? This is the biggest issue. I posted on the PR but it mostly means a whole new way of installing python and virtual environments that's currently incompatible with the way we do instlaations.

OK, I understand from here and there that this is a technical problem that nobody yet has a solution to. I'll expect to let this hibernate for a while.