# TPDE: A Fast Adaptable Compiler Back-End Framework

**URL:** https://discourse.julialang.org/t/tpde-a-fast-adaptable-compiler-back-end-framework/129576
**Category:** Offtopic
**Created:** [June 2, 2025, 6:45pm UTC](https://discourse.julialang.org/t/tpde-a-fast-adaptable-compiler-back-end-framework/129576 "2025-06-02T18:45:11Z")
**Posts on this page:** 1
**Showing post:** 12

<div class="post-metadata">

### Author: ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)
#### Post date: [September 3, 2025, 3:21pm UTC](https://discourse.julialang.org/t/tpde-a-fast-adaptable-compiler-back-end-framework/129576/12 "2025-09-03T15:21:21Z")

</div>

It might be easier to use this TPDE-LLVM (for LLVM compatibility), or as I suggest, bypass LLVM (like Zig is doing; there no longer default):

> [@Would it be possible to write LLVM in Julia?](https://discourse.julialang.org/t/would-it-be-possible-to-write-llvm-in-julia/103925/7):
>
> yes, but I believe better to bypass LLVM (for non-default Julia [mode]) as Zig did: Debug compilation is 5 times faster with Zig’s x86 Backend selected by default Using the self-hosted x86 backend also means you are not subject to the effects of upstream LLVM bugs, of which we are currently tracking over 60. In fact, the self-hosted x86 backend already passes a larger subset of our “behavior test suite” than the LLVM backend does (1984/2008 vs 1977/2008). In other words, this backend pro…

---

_[View the full topic](https://discourse.julialang.org/t/tpde-a-fast-adaptable-compiler-back-end-framework/129576)._