[Backport 3.3] [Bug #20085] Use consistent default options for -mbranch-protection
#9385
Conversation
We need to use the same options for both C compiler and assembler
when `-mbranch-protection` is guessed by configure. Otherwise,
`coroutine/arm64/Context.{h,S}` will use incompatible PAC strategies.
|
@nurse Can this backport for 3.3 Fiber segfault be merged? |
Backports the following patches which fixes critical or major issues: - ruby/ruby#9457 - ruby/ruby#9415 - https://bugs.ruby-lang.org/issues/20184 ruby/ruby#9498 - https://bugs.ruby-lang.org/issues/20085 ruby/ruby#9385
|
The bug is closed so I'm commenting here, but I don't understand, it says it's going to be backported to 3.3.1 but there is no 3.3.1 release? |
It's going to be backported to 3.3.1 as a future release -- presumably some months from now -- will have this patch already baked in. Unfortunately, Here's hoping they release a 3.3.0 patch soon :) Can't wait to start using it, but we suffer from this bug too. |
|
@dorianmarie "Status" field is only for master branch, not backport status. You should look "Backport" fields. |
So it says it's going to be backported to 3.3 ("required") |
|
Any guess as to when the backport to 3.3.0 will land? Our 3.3.0 upgrade is on hold, wondering if we should wait or employ a workaround. |
|
GitHub is not discussion place for release engineering. Please use https://bugs.ruby-lang.org/issues/20085 |
Cherry-pick 02973b7 to fix a regression in 3.3.0 release https://bugs.ruby-lang.org/issues/20085
We need to use the same options for both C compiler and assembler when
-mbranch-protectionis guessed by configure. Otherwise,coroutine/arm64/Context.{h,S}will use incompatible PAC strategies.