aboutsummaryrefslogtreecommitdiff
path: root/gcc/gcc-urlifier.cc
diff options
context:
space:
mode:
authorKewen Lin <linkw@linux.ibm.com>2024-01-09 23:05:13 -0600
committerKewen Lin <linkw@linux.ibm.com>2024-01-09 23:05:13 -0600
commitcb62101787555b7b32607b431fdfe6fcc8f3830f (patch)
treed7fcceff501debd853347c808661394ada0efb03 /gcc/gcc-urlifier.cc
parent1d1faf326474a20c8622007af1bdc9730397a427 (diff)
downloadgcc-cb62101787555b7b32607b431fdfe6fcc8f3830f.zip
gcc-cb62101787555b7b32607b431fdfe6fcc8f3830f.tar.gz
gcc-cb62101787555b7b32607b431fdfe6fcc8f3830f.tar.bz2
strub: Only unbias stack point for SPARC_STACK_BOUNDARY_HACK [PR113100]
As PR113100 shows, the unbiasing introduced by r14-6737 can cause the scrubbing to overrun and screw some critical data on stack like saved toc base consequently cause segfault. By checking PR112917, IMHO we should keep this unbiasing guarded under SPARC_STACK_BOUNDARY_HACK (TARGET_ARCH64 && TARGET_STACK_BIAS), similar to some existing code special treating SPARC stack bias. PR middle-end/113100 gcc/ChangeLog: * builtins.cc (expand_builtin_stack_address): Guard stack point adjustment with SPARC_STACK_BOUNDARY_HACK.
Diffstat (limited to 'gcc/gcc-urlifier.cc')
0 files changed, 0 insertions, 0 deletions