© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Specific build flags _might_ have unique error, warning, or failure strings that show up in the log. I could not find any such unique string in libunwind logs built with different -mbranch-protection flags. From the u-boot log [0] `error: ‘-fcf-protectio
It makes some sense that the stack unwind library conflicts with mbranch-protection. I'll take that as a positive sign that the impact is low for this flag :)
Anything with a vendored version of libunwind needs triage. The libunwind package has not rebuilt binaries recently [1], when it rebuilds it will misbuild and impact reverse dependencies.
I had hoped that the 19.10 introduction of -fcf-protection [2] would have lightened impact, but new problems are popping up [0]. Re-triaging old `-fcf\-protection` LP bug reports seems worthwhile. Retpoline or other uses of -mindirect-branch with -fcf-protection should be triaged [3].
Searching bug trackers from other distros might reveal packages worth triaging.
[0] https:/
[1] https:/
[2] https:/
[3] https:/