You are not logged in.
- Topics: Active | Unanswered
#1 2025-01-09 21:36:09
- joshlangley
- Member
- Registered: 2022-09-20
- Posts: 3
What is the rational behind force-frame-pointers=yes for rust packages
I was pacdiffing through my configs recently and discovered a change to the default rustc flags in /etc/makepkg.conf.d/rust.conf to include force-frame-pointers=yes. Considering the relevant entry in the Rust book (https://doc.rust-lang.org/rustc/codegen-options) is adjacent to the force-unwind-tables option, I assume this is a frame pointer unwinding vs table unwinding thing. I legitimately know nothing of the topic other than that these two different strategies exist and generally how they work.
I tried learning about the practical differences between these two strategies and am finding mostly debate about which is superior.
The most helpful resources I've found are these:
According to this Stackoverflow answer this option overrides the Rust default.
I'm curious to know the rationale behind overriding this option for Arch packages. I'm not as interested in reasons one is theoretically superior, but am open to investigating any resources on the matter. At the end of the day I'm just curious and want to learn about the topic in general.
Thanks for your time!
Edit: Corrected formatting to use BBCode rather than Markdown.
Last edited by joshlangley (2025-01-09 22:03:47)
Offline
#2 2025-01-09 23:11:04
- gromit
- Package Maintainer (PM)
- From: Germany
- Registered: 2024-02-10
- Posts: 905
- Website
Re: What is the rational behind force-frame-pointers=yes for rust packages
Offline