1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Disable __builtin_setjmp usage on linux-aarch64

Browse Source 
It is questionable whether __builtin_setjmp should default to yes
at all, but since it appears to still have problems on this platform,
it seems safest to disable it.

Fixes [Bug #14480]
This commit is contained in:
Jeremy Evans 2023-08-23 14:43:06 -07:00
parent 8f7d08137e
commit 029d92b898
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
configure.ac
View File

@ -1259,7 +1259,8 @@ main()
# __builtin_longjmp in ppc64* Linux does not restore # __builtin_longjmp in ppc64* Linux does not restore
# the TOC register (r2), which is problematic # the TOC register (r2), which is problematic
# when a global exit happens from JITted .so code. # when a global exit happens from JITted .so code.
AS_CASE(["$target_cpu"], [powerpc64*], [ # __builtin_setjmp can have issues on arm64 linux (see [Bug #14480]).
AS_CASE(["$target_cpu"], [powerpc64*|arm64|aarch64], [
ac_cv_func___builtin_setjmp=no ac_cv_func___builtin_setjmp=no
]) ])
# With gcc-8's -fcf-protection, RJIT's __builtin_longjmp fails. # With gcc-8's -fcf-protection, RJIT's __builtin_longjmp fails.