ziglang/zig
262
5.9k
Fork
You've already forked zig
763

WIP: bring back plan9 #36053

Draft
Arusekk wants to merge 4 commits from arusekk/plan9 into master AGit
pull from: arusekk/plan9
merge into: ziglang:master
ziglang:master
ziglang:std.zig.Ast.ParseOptions
ziglang:elfv2
ziglang:spork8
ziglang:restricted
ziglang:0.16.x
ziglang:panic-rewrite
ziglang:parking-futex-lockfree
ziglang:windows-Io-cleanup
ziglang:Io-watch
ziglang:ParseCommandLineOptions
ziglang:windows-async-files
ziglang:poll-ring
ziglang:debug-file-leaks-differently
ziglang:debug-file-leaks
ziglang:ProcessPrng
ziglang:elfv2-dyn
ziglang:jobserver
ziglang:threadtheft
ziglang:io-threaded-no-queue
ziglang:0.15.x
ziglang:Io.net
ziglang:comptime-allocator
ziglang:restricted-function-pointers
ziglang:cli
ziglang:wasm-linker-writer
ziglang:wrangle-writer-buffering
ziglang:sha1-stream
ziglang:async-await-demo
ziglang:fixes
ziglang:0.14.x
ziglang:ast-node-methods
ziglang:macos-debug-info
ziglang:make-vs-configure
ziglang:fuzz-macos
ziglang:sans-aro
ziglang:ArrayList-reserve
ziglang:incr-bug
ziglang:llvm-ir-nosanitize-metadata
ziglang:ci-tarballs
ziglang:ci-scripts
ziglang:threadpool
ziglang:0.12.x
ziglang:new-pkg-hash
ziglang:json-diagnostics
ziglang:more-doctests
ziglang:rework-comptime-mutation
ziglang:0.11.x
ziglang:ci-perf-comment
ziglang:stage2-async
ziglang:0.10.x
ziglang:autofix
ziglang:0.9.x
ziglang:aro
ziglang:hcs
ziglang:0.8.x
ziglang:0.7.x
First-time contributor
Copy link

This is a work in progress. I would appreciate some feedback before working more on it. I made it compile an empty fn main() void {} for -target x86_64-plan9 -ofmt=elf, but it still needs some love going forward. Sorry if this description is ugly, but I had no way of seeing how it looks, because I pushed the PR via so-called AGit workflow (forking is currently broken on Codeberg).

This is a work in progress. I would appreciate some feedback before working more on it. I made it compile an empty `fn main() void {}` for -target x86_64-plan9 -ofmt=elf, but it still needs some love going forward. Sorry if this description is ugly, but I had no way of seeing how it looks, because I pushed the PR via so-called AGit workflow (forking is currently broken on Codeberg).
lib improvements
Some checks are pending
ci / aarch64-freebsd-debug (pull_request) Blocked by required conditions
ci / aarch64-freebsd-release (pull_request) Blocked by required conditions
ci / aarch64-linux-debug (pull_request) Blocked by required conditions
ci / aarch64-linux-release (pull_request) Blocked by required conditions
ci / aarch64-netbsd-debug (pull_request) Blocked by required conditions
ci / aarch64-netbsd-release (pull_request) Blocked by required conditions
ci / aarch64-macos-debug (pull_request) Blocked by required conditions
ci / aarch64-macos-release (pull_request) Blocked by required conditions
ci / loongarch64-linux-debug (pull_request) Blocked by required conditions
ci / loongarch64-linux-release (pull_request) Blocked by required conditions
ci / powerpc64le-linux-debug (pull_request) Blocked by required conditions
ci / powerpc64le-linux-release (pull_request) Blocked by required conditions
ci / riscv64-linux-debug (pull_request) Blocked by required conditions
ci / riscv64-linux-release (pull_request) Blocked by required conditions
ci / s390x-linux-debug (pull_request) Blocked by required conditions
ci / s390x-linux-release (pull_request) Blocked by required conditions
ci / x86_64-freebsd-debug (pull_request) Blocked by required conditions
ci / x86_64-freebsd-release (pull_request) Blocked by required conditions
ci / x86_64-linux-debug (pull_request) Blocked by required conditions
ci / x86_64-linux-debug-llvm (pull_request) Blocked by required conditions
ci / x86_64-linux-release (pull_request) Blocked by required conditions
ci / x86_64-netbsd-debug (pull_request) Blocked by required conditions
ci / x86_64-netbsd-release (pull_request) Blocked by required conditions
ci / x86_64-openbsd-debug (pull_request) Blocked by required conditions
ci / x86_64-openbsd-release (pull_request) Blocked by required conditions
ci / x86_64-windows-debug (pull_request) Blocked by required conditions
ci / x86_64-windows-release (pull_request) Blocked by required conditions
a776b5f0ba
Author
First-time contributor
Copy link

Okay, it worked. So this code so far has been mostly (but not only) an improved git revert so that everything compiles at least.

Now, I am a bit stuck, there are several options on how I go forward with this:

  • splitting even the current changeset into smaller PRs (I will probably do it this way if I get no directional feedback, being an open source maintainer myself, I like small changes the most), or
  • reworking this to be more directed and step-by-step, but keeping everything in a single massive PR that brings user-visible functionality.

Currently the reason I am stuck is that compiling

pub fn main() void {}

needs a memmove implementation, and even with a memmove it still reports unresolved relocations somehow.

I am compiling with

zig build-exe empty.zig -target x86_64-plan9 -ofmt=elf -fsingle-threaded -fcompiler-rt

My questions:

  1. Should I first split simple improvements out of these changes, and submit them separately? (I can see there are conflicts already; I can take it as a yes)
  2. Why is compiler_rt not included into the binary when running zig build-exe -target x86_64-plan9 -ofmt=elf -fsingle-threaded -fcompiler-rt planback.zig? (mystery no. 1)
  3. Why on earth are there relocations when running zig build-exe -target x86_64-plan9 -ofmt=plan9 -fsingle-threaded -fcompiler-rt planback.zig? How to even debug it? Plan 9 famously does not support relocations on purpose, they should be irrelevant when doing static linking! Note that the only binary format implemented in Zig is the executable format, the object format is so much different, and architecture-specific that I do not even want to look at it. (mystery no. 2)
  4. Do you want some CI for testing the resulting Plan 9 binaries? There is https://uglendix.dev (a Wine analogue by yours truly), which facilitates running unmodified Plan 9 binaries on Linux - in Docker or otherwise. It runs binaries compiled with Zig 0.13.0 just fine.
Okay, it worked. So this code so far has been mostly (but not only) an improved git revert so that everything compiles at least. Now, I am a bit stuck, there are several options on how I go forward with this: - splitting even the current changeset into smaller PRs (I will probably do it this way if I get no directional feedback, being an open source maintainer myself, I like small changes the most), or - reworking this to be more directed and step-by-step, but keeping everything in a single massive PR that brings user-visible functionality. Currently the reason I am stuck is that compiling ``` pub fn main() void {} ``` needs a memmove implementation, and even with a memmove it still reports unresolved relocations somehow. I am compiling with ``` zig build-exe empty.zig -target x86_64-plan9 -ofmt=elf -fsingle-threaded -fcompiler-rt ``` My questions: 1. Should I first split simple improvements out of these changes, and submit them separately? (I can see there are conflicts already; I can take it as a yes) 2. Why is compiler_rt not included into the binary when running `zig build-exe -target x86_64-plan9 -ofmt=elf -fsingle-threaded -fcompiler-rt planback.zig`? (mystery no. 1) 3. Why on earth are there relocations when running `zig build-exe -target x86_64-plan9 -ofmt=plan9 -fsingle-threaded -fcompiler-rt planback.zig`? How to even debug it? Plan 9 famously does not support relocations on purpose, they should be irrelevant when doing static linking! Note that the only binary format implemented in Zig is the executable format, the object format is so much different, and architecture-specific that I do not even want to look at it. (mystery no. 2) 4. Do you want some CI for testing the resulting Plan 9 binaries? There is https://uglendix.dev (a Wine analogue by yours truly), which facilitates running unmodified Plan 9 binaries on Linux - in Docker or otherwise. It runs binaries compiled with Zig 0.13.0 just fine.
First-time contributor
Copy link

dafuq!? where do you even obtain a copy of Plan9 to test this on???

dafuq!? where do you even obtain a copy of Plan9 to test this on???
Author
First-time contributor
Copy link

@bpavuk Well, since compilation is a computational task - converting source code (a sequence of bytes) into an executable (a sequence of bytes) - you can run compilation of Zig source code into a Plan9 binary by running the Zig compiler on Linux, or even on Windows if you like. Then you can inspect it using a reverse engineering tool, like Radare2 or Ghidra, or use a VM or an API translation layer to execute it. Uglendix is the latter.

Currently, there is no binary produced, even. The computation fails earlier, and I need help figuring out why.

@bpavuk Well, since compilation is a computational task - converting source code (a sequence of bytes) into an executable (a sequence of bytes) - you can run compilation of Zig source code into a Plan9 binary by running the Zig compiler on Linux, or even on Windows if you like. Then you can inspect it using a reverse engineering tool, like Radare2 or Ghidra, or use a VM or an API translation layer to execute it. Uglendix is the latter. Currently, there is no binary produced, even. The computation fails earlier, and I need help figuring out why.
Contributor
Copy link

@bpavuk wrote in #36053 (comment):

dafuq!? where do you even obtain a copy of Plan9 to test this on???

Plan9: https://plan9.io/plan9/download.html
9legacy: http://9legacy.org/download.html
9front: https://9front.org/download/

@bpavuk wrote in https://codeberg.org/ziglang/zig/pulls/36053#issuecomment-18627176: > dafuq!? where do you even obtain a copy of Plan9 to test this on??? Plan9: https://plan9.io/plan9/download.html 9legacy: http://9legacy.org/download.html 9front: https://9front.org/download/
First-time contributor
Copy link

@Arusekk @K4 this is awesome, I wish you luck. it would be interesting to follow this as an example of adding OS support

@Arusekk @K4 this is awesome, I wish you luck. it would be interesting to follow this as an example of adding OS support
Contributor
Copy link

@bpavuk wrote in #36053 (comment):

@K4 this is awesome, I wish you luck.

Maybe I will help in the future, but I am not involved right now. I didn't get to a workinkg GUI with 9front when I tried and don't have actual experience with Plan9 or 9front, but I plan to in the future.
I hope that zig will get to a good state on both versions.

@bpavuk wrote in https://codeberg.org/ziglang/zig/pulls/36053#issuecomment-18628685: > @K4 this is awesome, I wish you luck. Maybe I will help in the future, but I am not involved right now. I didn't get to a workinkg GUI with 9front when I tried and don't have actual experience with Plan9 or 9front, but I plan to in the future. I hope that zig will get to a good state on both versions.
Some checks are pending
ci / aarch64-freebsd-debug (pull_request) Blocked by required conditions
ci / aarch64-freebsd-release (pull_request) Blocked by required conditions
ci / aarch64-linux-debug (pull_request) Blocked by required conditions
Required
Details
ci / aarch64-linux-release (pull_request) Blocked by required conditions
Required
Details
ci / aarch64-netbsd-debug (pull_request) Blocked by required conditions
ci / aarch64-netbsd-release (pull_request) Blocked by required conditions
ci / aarch64-macos-debug (pull_request) Blocked by required conditions
Required
Details
ci / aarch64-macos-release (pull_request) Blocked by required conditions
Required
Details
ci / loongarch64-linux-debug (pull_request) Blocked by required conditions
ci / loongarch64-linux-release (pull_request) Blocked by required conditions
ci / powerpc64le-linux-debug (pull_request) Blocked by required conditions
Required
Details
ci / powerpc64le-linux-release (pull_request) Blocked by required conditions
Required
Details
ci / riscv64-linux-debug (pull_request) Blocked by required conditions
ci / riscv64-linux-release (pull_request) Blocked by required conditions
ci / s390x-linux-debug (pull_request) Blocked by required conditions
Required
Details
ci / s390x-linux-release (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-freebsd-debug (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-freebsd-release (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-linux-debug (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-linux-debug-llvm (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-linux-release (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-netbsd-debug (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-netbsd-release (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-openbsd-debug (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-openbsd-release (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-windows-debug (pull_request) Blocked by required conditions
Required
Details
ci / x86_64-windows-release (pull_request) Blocked by required conditions
Required
Details
This pull request has changes conflicting with the target branch.
  • lib/std/os/plan9.zig
  • src/codegen.zig
  • src/codegen/x86_64/Emit.zig
  • src/link.zig
Some workflows are waiting to be reviewed.
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin +refs/pull/36053/head:arusekk/plan9
git switch arusekk/plan9
Sign in to join this conversation.
No reviewers
Labels
Clear labels
abi/f32
abi/ilp32
abi/sf
accepted
This proposal is planned.
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
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
An issue related to debug information (e.g. DWARF) produced by the Zig compiler.
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
An issue related to Zig's integrated fuzz testing.
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.
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
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
An issue related to project infrastructure, e.g. continuous integration.
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
abi/f32
abi/ilp32
abi/sf
accepted
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
backend/c
backend/llvm
backend/self-hosted
binutils
breaking
build system
debug info
docs
error message
frontend
fuzzing
incremental
lib/c
lib/compiler-rt
lib/cxx
lib/std
lib/tsan
lib/ubsan-rt
lib/unwind
linking
miscompilation
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
release notes
testing
zig cc
zig fmt
zig reduce
bounty
bug
contributor-friendly
downstream
enhancement
infra
optimization
question
regression
upstream
use case
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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!36053
Reference in a new issue
ziglang/zig
No description provided.
Delete branch "arusekk/plan9"

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?