zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software. https://ziglang.org

Age	Commit message (Collapse)	Author
2025-08-28	std.debug: remove `@frameAddress()` "UAF"	mlugg
	We can't call `@frameAddress()` and then immediately `return`! That invalidates the frame. This usually isn't a problem, because the stack walk `next` call will probably have a stack frame and it will probably be at the exact same address, but neither of those is a guarantee. On powerpc, presumably some unfortunate inlining was going on, so this frame was indeed invalidated when we started walking frames. We need to explicitly pass `@frameAddress` into any function which will return before we actually walk the stack. Pretty simple patch. Resolves: #24970
2025-07-16	zig fmt	Andrew Kelley

2025-02-17	std.Target: Remove functions that just wrap component functions.	Alex Rønne Petersen
	Functions like isMinGW() and isGnuLibC() have a good reason to exist: They look at multiple components of the target. But functions like isWasm(), isDarwin(), isGnu(), etc only exist to save 4-8 characters. I don't think this is a good enough reason to keep them, especially given that: * It's not immediately obvious to a reader whether target.isDarwin() means the same thing as target.os.tag.isDarwin() precisely because isMinGW() and similar functions do look at multiple components. * It's not clear where we would draw the line. The logical conclusion before this commit would be to also wrap Arch.isX86(), Os.Tag.isSolarish(), Abi.isOpenHarmony(), etc... this obviously quickly gets out of hand. * It's nice to just have a single correct way of doing something.
2024-03-14	chore: Fix some typos	Ahmed

2023-11-19	test: update remaining code to fix 'var is never mutated' errors	mlugg

2023-07-20	test: disable omit_frame_pointer unwinding tests on aarch64-macos	kcbanner
	dwarf: handle signal frame CIE flag