Skip to content

Blog fixes #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
certik merged 5 commits into from
Jul 28, 2023
Merged

Blog fixes #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
1b6693e
fixes
Smit-create Jul 28, 2023
2e481e2
typos
Smit-create Jul 28, 2023
3e7235a
add line breaks
Smit-create Jul 28, 2023
8874d9d
line break after each table
Smit-create Jul 28, 2023
dbbd78d
add system info table
Smit-create Jul 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions content/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,19 @@ features that are being implemented.

## Works today

* **Best possible performance for numerical, array-oriented code**
* **Best possible performance for numerical, array-oriented code**
LPython gives you the speed you need for your numerical, array-oriented code. With LPython, you can write Python code that is as fast as C or C++. This is because LPython compiles your code to optimized machine code, which is the fastest way to run code on a computer.

* **Code compatability with CPython**
* **Code compatability with CPython**
If LPython compiles and runs a code, then it will run in CPython.

* **Seamless interoperability with CPython**
* **Seamless interoperability with CPython**
LPython can call functions in CPython libraries. This feature permits “break-out” to Numpy, TensorFlow, PyTorch, and even to matplotlib. The break-outs will run at ordinary (slow) Python speeds, but LPython accelerates the mathematical portions to near maximum speed.

* **Just-In-Time (JIT) compilation**
LPython also supports Just-in-time compilation which requires only decorating Python function with @lpython. One can also specify the desired backend, as in, `@lpython(backend=“c”)` or `@lpython(backend=“llvm”)`. Only C is supported at present; LLVM and others will be added in the near future.
* **Just-In-Time (JIT) compilation**
LPython also supports Just-in-time compilation which requires only decorating Python function with `@lpython`. One can also specify the desired backend, as in, `@lpython(backend=“c”)` or `@lpython(backend=“llvm”)`. Only C is supported at present; LLVM and others will be added in the near future.

* **Clean, modular design, usable as a library**
* **Clean, modular design, usable as a library**
LPython is structured around two independent modules, AST (Abstract Syntax
Tree) and ASR (Abstract Semantic Representation), both of which are
standalone (completely independent of the rest of LPython) and users are
Expand All @@ -26,13 +26,13 @@ features that are being implemented.
[Developer Tutorial](https://docs.lfortran.org/developer_tutorial/) documents for
more details.

* **Create executables**
* **Create executables**
It can create fast optimized executables unlike other interpreted compilers.

* **Runs on Linux, Mac, Windows and WebAssembly**
* **Runs on Linux, Mac, Windows and WebAssembly**
All four platforms are regularly tested by our CI.

* **Several backends**
* **Several backends**
The LLVM can be used to compile to binaries and for interactive usage. The
C/C++ backend translates Python code to a readable C/C++ code. The x86 backend
allows very fast compilation directly to x86 machine code. The WebAssembly
Expand All @@ -43,20 +43,20 @@ features that are being implemented.

These features are under development:

* **Interactive, Jupyter support**
* **Interactive, Jupyter support**
LPython is coming soon to Jupyter. It can be used as a Jupyter kernel,
allowing Python/Julia-style rapid prototyping and an exploratory
workflow (`conda install jupyter lpython`).
It can also be used from the command-line with an interactive prompt
(REPL).

* **Support for diverse hardware**
* **Support for diverse hardware**
LLVM makes it possible to run LPython on diverse hardware.
We plan to support a wide range of hardware platforms, including:

CPUs: compile Python code to run on CPUs of all architectures, including x86, ARM, and POWER.
GPUs: compile Python code to run on GPUs from NVIDIA, AMD, and Intel.
TPUs: compile Python code to run on TPUs from Google.
- CPUs: compile Python code to run on CPUs of all architectures, including x86, ARM, and POWER.
- GPUs: compile Python code to run on GPUs from NVIDIA, AMD, and Intel.
- TPUs: compile Python code to run on TPUs from Google.

Please vote on issues in our [issue tracker] that you want us to prioritize
(feel free to create new ones if we are missing anything).
Expand Down
50 changes: 40 additions & 10 deletions content/blog/lpython_mvp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ LPython implements several machine-independent optimisations via ASR-to-ASR pass
5. Transforming division to multiplication operation
6. Fused multiplication and addition

All optimizations are applied via one command-line argument, --fast. To select individual optimizations instead, write a command-line argument like the following:
All optimizations are applied via one command-line argument, `--fast`. To select individual optimizations instead, write a command-line argument like the following:

`--pass=inline_function_calls,loop_unroll`

Expand Down Expand Up @@ -95,7 +95,7 @@ print(res)
./a.out 0.01s user 0.00s system 89% cpu 0.012 total
```

You can see that it's very fast. It's still plenty fast with the C backend via the command-line argument --backend=c:
You can see that it's very fast. It's still plenty fast with the C backend via the command-line argument `--backend=c`:

```zsh
% time lpython /Users/czgdp1807/lpython_project/debug.py --backend=c
Expand All @@ -107,13 +107,13 @@ Note that time lpython `/Users/czgdp1807/lpython_project/debug.py --backend=c` i

### Just-In-Time Compilation

Just-in-time compilation in LPython requires only decorating Python function with @lpython. The decorator takes an option for specifying the desired backend, as in, @lpython(backend="c") or @lpython(backend="llvm"). Only C is supported at present; LLVM and others will be added in the near future. The decorator also propagates backend-specific options. For example
Just-in-time compilation in LPython requires only decorating Python function with `@lpython`. The decorator takes an option for specifying the desired backend, as in, `@lpython(backend="c")` or `@lpython(backend="llvm")`. Only C is supported at present; LLVM and others will be added in the near future. The decorator also propagates backend-specific options. For example

```python
@lpython(backend="c",
backend_optimization_flags=["-ffast-math",
"-funroll-loops",
"-O1"])
backend_optimization_flags=["-ffast-math",
"-funroll-loops",
"-O1"])
```

Note that by default C backend is used without any optimisation flags.
Expand Down Expand Up @@ -187,7 +187,7 @@ def get_email(text):
lpython@lcompilers.org
```

Note: The `@pythoncall` and `@lpython` decorators are presently supported with just the `C` backend but eventually will work with the LLVM backend and that's work in progress.
*Note*: The `@pythoncall` and `@lpython` decorators are presently supported with just the `C` backend but eventually will work with the LLVM backend and that's work in progress.


## Benchmarks and Demos
Expand All @@ -200,8 +200,13 @@ We compare JIT compilation of LPython to Numba on **summation of all the element

**System Information**

Softwares - The numba version used is `numba-0.57.1`, LPython commit is `a39430386a0e7ea5de2f569e27229017dff78330` and Python version is `Python 3.10.4`.
| Compiler | Version |
|---|---|
| Numba | 0.57.1 |
| LPython | 0.19.0 |
| Python | 3.10.4 |

<br/>
<!-- Add your systems like System - Linux, System - Windows, etc and then add the results for your System in the tables that follow -->

**Summation of all the elements of a 1-D array**
Expand Down Expand Up @@ -261,6 +266,8 @@ test()
| Numba | 0.20 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| LPython | 0.32 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.60 |

<br/>

| Compiler | Execution Time (s) | System | Relative |
|---|---|---|---|
| LPython | 0.013 | Apple M1 MBP 2020 | 1.00 |
Expand All @@ -272,6 +279,7 @@ test()
| LPython | 0.048 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| Numba | 0.048 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |

<br/>
<!-- TODO: Write a summary of the results -->

**Pointwise multiplication of two 1-D arrays**
Expand Down Expand Up @@ -325,6 +333,8 @@ test()
| Numba | 0.21 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| LPython | 0.31 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.48 |

<br/>

| Compiler | Execution Time (s) | System | Relative |
|---|---|---|---|
| Numba | 0.041 | Apple M1 MBP 2020 | 1.00 |
Expand All @@ -336,6 +346,7 @@ test()
| Numba | 0.21 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| LPython | 0.21 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |

<br/>
<!-- TODO: Write a summary of the results -->

**Insertion sort on lists**
Expand Down Expand Up @@ -405,6 +416,8 @@ test()
| Numba | 0.35 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| LPython | 0.37 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.06 |

<br/>

| Compiler | Execution Time (s) | System | Relative |
|---|---|---|---|
| LPython | 0.11 | Apple M1 MBP 2020 | 1.00 |
Expand All @@ -416,6 +429,7 @@ test()
| LPython | 0.10 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| Numba | 0.36 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 3.60 |

<br/>
<!-- TODO: Write a summary of the results -->

**Quadratic-time implementation of the Dijkstra shortest-path algorithm on a fully connected graph**
Expand Down Expand Up @@ -538,6 +552,8 @@ test()
| LPython | 1.08 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| Numba | 1.69 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.56 |

<br/>

| Compiler | Execution Time (s) | System | Relative |
|---|---|---|---|
| LPython | 0.23 | Apple M1 MBP 2020 | 1.00 |
Expand All @@ -549,6 +565,7 @@ test()
| LPython | 0.87 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 1.00 |
| Numba | 1.95 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 2.24 |

<br/>
<!-- TODO: Write a summary of the results -->

### Ahead-of-Time (AoT) Compilation
Expand All @@ -557,7 +574,15 @@ Next, we see how LPython compares to other AoT compilers and to the standard CPy

**System Information**

The Clang++ version used is `14.0.3`, `g++` version is `11.3.0`, LPython commit is `a39430386a0e7ea5de2f569e27229017dff78330` and Python version is `Python 3.10.4`.

| Compiler | Version |
|---|---|
| clang++ | 14.0.3 |
| g++ | 11.3.0 |
| LPython | 0.19.0 |
| Python | 3.10.4 |

<br/>

**Quadratic-time implementation of the Dijkstra shortest-path algorithm on a fully connected graph**

Expand Down Expand Up @@ -697,6 +722,8 @@ int main() {
| g++ | 1.358 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 2.21 |
| Python | 7.365 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 12.01 |

<br/>

Note the optimization flags furnished to each compiler.

| Compiler/Interpreter | Optimization flags used |
Expand All @@ -706,6 +733,8 @@ Note the optimization flags furnished to each compiler.
| g++ | `-ffast-math -funroll-loops -O3`|
| Python | - |

<br/>

<!-- TODO: Write a summary of the results -->

**Floyd-Warshall algorithm on array representation of graphs**
Expand Down Expand Up @@ -806,7 +835,7 @@ int main() {
| LPython | 2.933 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 4.22 |
| Python | 440.588 | AMD Ryzen 5 2500U (Ubuntu 22.04) | 633.94 |


<br/>
<!-- TODO: Remove above line if the following table looks good.-->

Note the optimization flags furnished to each compiler.
Expand All @@ -818,6 +847,7 @@ Note the optimization flags furnished to each compiler.
| g++ | `-ffast-math -funroll-loops -O3`|
| Python | - |

<br/>
<!-- TODO: Write a summary of the results -->

### Interoperability with CPython
Expand Down