aboutsummaryrefslogtreecommitdiff
path: root/src/codegen.zig
diff options
context:
space:
mode:
authormlugg <mlugg@mlugg.co.uk>2025-06-01 22:57:59 +0100
committermlugg <mlugg@mlugg.co.uk>2025-06-12 13:55:40 +0100
commit5ab307cf47b1f0418d9ed4ab56df6fb798305c20 (patch)
treee6efda29764d1fdaa92c40cce951f13c394facba /src/codegen.zig
parent9eb400ef19391261a3b61129d8665602c89959c5 (diff)
downloadzig-5ab307cf47b1f0418d9ed4ab56df6fb798305c20.tar.gz
zig-5ab307cf47b1f0418d9ed4ab56df6fb798305c20.zip
compiler: get most backends compiling again
As of this commit, every backend other than self-hosted Wasm and self-hosted SPIR-V compiles and (at least somewhat) functions again. Those two backends are currently disabled with panics. Note that `Zcu.Feature.separate_thread` is *not* enabled for the fixed backends. Avoiding linker references from codegen is a non-trivial task, and can be done after this branch.
Diffstat (limited to 'src/codegen.zig')
-rw-r--r--src/codegen.zig2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/codegen.zig b/src/codegen.zig
index 2c2524257c..ea57aaf89c 100644
--- a/src/codegen.zig
+++ b/src/codegen.zig
@@ -182,7 +182,7 @@ pub fn emitFunction(
/// in the pipeline. Any information needed to call emit must be stored in MIR.
/// This is `undefined` if the backend supports the `separate_thread` feature.
air: *const Air,
-) Allocator.Error!void {
+) CodeGenError!void {
const zcu = pt.zcu;
const func = zcu.funcInfo(func_index);
const target = zcu.navFileScope(func.owner_nav).mod.?.resolved_target.result;