Interesting! If more are to be added, I wonder if it will be possible to use Zig for gameboy development (original b/w gamboy, and gameboy color or gameboy advanced/SP, for example)

mark-rushakoff commented

2026年02月26日 18:04:23 +01:00

Copy link

I have successfully run some hello world style Zig code in the Ares emulator for Nintendo 64. I've seen at least one other person with a blog post saying they've written Zig running on N64. I assume there are more out there. The N64 uses a MIPS architecture that LLVM supports.

GameBoy Advance uses ARM7, and there are several existing resources about people writing GBA homebrew with Zig.

alexrp commented

2026年02月26日 19:34:21 +01:00

Author

Owner

Copy link

To be clear, I think it only makes sense to add std.Target.Os.Tag members for consoles that have some sort of operating system or OS-like services provided by the BIOS, or similar. Failing that, you're really just doing freestanding programming, which we already have a tag for.

To be clear, I think it only makes sense to add `std.Target.Os.Tag` members for consoles that have some sort of operating system or OS-like services provided by the BIOS, or similar. Failing that, you're really just doing freestanding programming, which we already have a tag for.

👀 1

hemisputnik commented

2026年02月27日 13:59:55 +01:00

Contributor

Copy link

Most homebrew tends to avoid calling these functions though, as a lot of them are terribly slow and sometimes even buggy (atof for example requires an absent FPU to be present).

https://psx-spx.consoledev.net/kernelbios/#bios-overview

The PSX has a BIOS which provides functions for accessing the hardware and a (very bad) libc implementation. You can call these functions by jumping to different offsets in RAM with a value in the R9 register (some are callable through a SYSCALL too): https://psx-spx.consoledev.net/kernelbios/#bios-function-summary Most homebrew tends to avoid calling these functions though, as a lot of them are terribly slow and sometimes even buggy ([`atof`](https://psx-spx.consoledev.net/kernelbios/#a0bh-atofsrc-uses-absent-cop1-fpu) for example requires an absent FPU to be present). https://psx-spx.consoledev.net/kernelbios/#bios-overview

Zorgatone commented

2026年02月27日 17:33:26 +01:00

Copy link

@alexrp wrote in #31341 (comment):

To be clear, I think it only makes sense to add std.Target.Os.Tag members for consoles that have some sort of operating system or OS-like services provided by the BIOS, or similar. Failing that, you're really just doing freestanding programming, which we already have a tag for.

Ah I see, yeah it makes sense thanks

@alexrp wrote in https://codeberg.org/ziglang/zig/issues/31341#issuecomment-11029742: > To be clear, I think it only makes sense to add `std.Target.Os.Tag` members for consoles that have some sort of operating system or OS-like services provided by the BIOS, or similar. Failing that, you're really just doing freestanding programming, which we already have a tag for. Ah I see, yeah it makes sense thanks

IridescentRose referenced this issue

2026年03月21日 06:53:43 +01:00

Add psp os #31609

alexrp commented

2026年05月04日 18:35:01 +02:00

Author

Owner

Copy link

@alexrp wrote in #31341 (comment):

PS2

https://github.com/llvm/llvm-project/pull/176666 will be in LLVM 23.

@alexrp wrote in https://codeberg.org/ziglang/zig/issues/31341#issue-3644882: > PS2 https://github.com/llvm/llvm-project/pull/176666 will be in LLVM 23.

👀 1 🚀 2

kassane commented

2026年06月07日 16:17:09 +02:00

Copy link

What's the PS3 support status?

https://github.com/ziglang/zig/issues/26020

What's the PS3 support status? - https://github.com/ziglang/zig/issues/26020

alexrp commented

2026年06月07日 18:06:43 +02:00

Author

Owner

Copy link

No idea. But if any target info for it is missing, it's certainly welcome.

👍 1

neoto commented

2026年06月07日 19:05:00 +02:00

Contributor

Copy link

@alexrp wrote in #31341 (comment):

To be clear, I think it only makes sense to add std.Target.Os.Tag members for consoles that have some sort of operating system or OS-like services provided by the BIOS, or similar. Failing that, you're really just doing freestanding programming, which we already have a tag for.

I have a working PSX target locally that does the same thing as Rust regarding the OS. Do you think that's fine for Zig as well or should I get rid of it?

alexrp commented

2026年06月07日 19:14:39 +02:00

Author

Owner

Copy link

I think the bespoke BIOS that's resident on the PSX is just enough for it to satisfy the criteria I laid out above. So PR welcome.

👍 1

alexrp added the

contributor-friendly

label

2026年06月07日 19:15:29 +02:00

kassane commented

2026年06月09日 22:49:15 +02:00

Copy link

No idea. But if any target info for it is missing, it's certainly welcome.

This is a work in progress. I'm trying to fix the issue so I can submit a patch to LLVM. I've made progress, as shown in the screenshot. I'll test it on the updated PS3-RealHardware (S-Slim), but for now I'm using an emulator with the latest PS3 firmware.
image

> No idea. But if any target info for it is missing, it's certainly welcome. This is a work in progress. I'm trying to fix the issue so I can submit a patch to LLVM. I've made progress, as shown in the screenshot. I'll test it on the updated PS3-RealHardware (S-Slim), but for now I'm using an emulator with the latest PS3 firmware. ![image](/attachments/54d37a3d-2c3b-451e-aafb-49f1a1cd722c)

image.png

93 KiB

👍 1 👀 3

neoto referenced this issue

2026年06月16日 17:23:22 +02:00

std.Target: add PSX #35810

alexrp referenced this issue from a commit

2026年07月07日 15:35:22 +02:00

std.Target: add switch (Nintendo Switch) Os tag

alexrp referenced this issue

2026年07月07日 15:36:03 +02:00

std.Target: add switch (Nintendo Switch) Os tag #36081

No Branch/Tag specified

Branches Tags

master

elfv2

spork8

restricted

0.16.x

panic-rewrite

parking-futex-lockfree

windows-Io-cleanup

Io-watch

ParseCommandLineOptions

windows-async-files

poll-ring

debug-file-leaks-differently

debug-file-leaks

ProcessPrng

elfv2-dyn

jobserver

threadtheft

io-threaded-no-queue

0.15.x

Io.net

comptime-allocator

restricted-function-pointers

cli

wasm-linker-writer

wrangle-writer-buffering

sha1-stream

async-await-demo

fixes

0.14.x

ast-node-methods

macos-debug-info

make-vs-configure

fuzz-macos

sans-aro

ArrayList-reserve

incr-bug

llvm-ir-nosanitize-metadata

ci-tarballs

ci-scripts

threadpool

0.12.x

new-pkg-hash

json-diagnostics

more-doctests

rework-comptime-mutation

0.11.x

ci-perf-comment

stage2-async

0.10.x

autofix

0.9.x

aro

hcs

0.8.x

0.7.x

Labels

Clear labels

This proposal is planned.

The web application for interactive documentation and generation of its assets.

backend/c

The C backend outputs C source code.

backend/llvm

The LLVM backend outputs an LLVM bitcode module.

backend/self-hosted

The self-hosted backends produce machine code directly.

binutils

Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.

breaking

Implementing this issue could cause existing code to no longer compile or have different behavior.

build system

The Zig build system - zig build, std.Build, the build runner, and package management.

debug info

docs

An issue with documentation, e.g. the language reference or standard library doc comments.

error message

This issue points out an error message that is unhelpful and should be improved.

frontend

Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.

fuzzing

incremental

Reuse of internal compiler state for faster compilation.

lib/c

This issue relates to Zig's libc implementation and/or vendored libcs.

lib/compiler-rt

This issue relates to Zig's compiler-rt library.

lib/cxx

This issue relates to Zig's vendored libc++ and/or libc++abi.

lib/std

This issue relates to Zig's standard library.

lib/tsan

This issue relates to Zig's vendored libtsan.

lib/ubsan-rt

This issue relates to Zig's ubsan-rt library.

lib/unwind

This issue relates to Zig's vendored libunwind.

linking

Zig's integrated object file and incremental linker.

miscompilation

The compiler reports success but produces semantically incorrect code.

This issue suggests language modifications. If it also has the "accepted" label then it is planned.

release notes

This issue or pull request should be mentioned in the release notes.

testing

This issue is related to testing the compiler, standard library, or other parts of Zig.

zig cc

Zig as a drop-in C-family compiler.

zig fmt

The Zig source code formatter.

zig reduce

The Zig source code reduction tool.

bounty

https://ziglang.org/news/announcing-donor-bounties

bug

Observed behavior contradicts documented or intended behavior.

contributor-friendly

This issue is limited in scope and/or knowledge of project internals.

downstream

An issue with a third-party project that uses this project.

enhancement

Solving this issue will likely involve adding new logic or components to the codebase.

infra

optimization

A task to improve performance and/or resource usage.

question

No questions on the issue tracker; use a community space instead.

regression

Something that used to work in a previous version stopped working

upstream

An issue with a third-party project that this project uses.

use case

Describes a real use case that is difficult or impossible, but does not propose a solution.

No labels

Milestone

Clear milestone

No items

No milestone

Unplanned

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

6 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ziglang/zig#31341

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?