Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better unwind table support + unwind protection in _start() and clone() #22035

Merged
merged 6 commits into from
Dec 13, 2024

Conversation

alexrp
Copy link
Member

@alexrp alexrp commented Nov 20, 2024

No description provided.

@alexrp
Copy link
Member Author

alexrp commented Nov 20, 2024

@jacobly0 can you take a look at the unwind protection I added and see if it makes sense to you?

Also cc @andrewrk @mlugg since this is adding a new @import("builtin").unwind_tables field.

Copy link
Member

@jacobly0 jacobly0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know anything about the unwind tables changes.

lib/std/os/linux/x86.zig Outdated Show resolved Hide resolved
@alexrp
Copy link
Member Author

alexrp commented Dec 6, 2024

Sent the musl patch upstream: https://www.openwall.com/lists/musl/2024/12/06/4

Going to wait a bit and see if there are any comments on it before merging this.

The goal here is to support both levels of unwind tables (sync and async) in
zig cc and zig build. Previously, the LLVM backend always used async tables
while zig cc was partially influenced by whatever was Clang's default.
The function is not marked .cantunwind for Arm/Thumb because of an LLVM
assembler bug: llvm/llvm-project#115891
Whatever was in the frame pointer register prior to clone() will no longer be
valid in the child process, so zero it to protect FP-based unwinders. Similarly,
mark the link register as undefined to protect DWARF-based unwinders.

This is only zeroing the frame pointer(s) on Arm/Thumb because of an LLVM
assembler bug: llvm/llvm-project#115891
Whatever was in the frame pointer register prior to clone() will no longer be
valid in the child process, so zero it to protect FP-based unwinders. This is
just an extension of what was already done for i386 and x86_64. Only applied
to architectures where the _start() code also zeroes the frame pointer.
@alexrp alexrp merged commit 130f7c2 into ziglang:master Dec 13, 2024
10 checks passed
@alexrp alexrp deleted the unwind-fixes branch December 13, 2024 02:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants