| commit | f98b772119882fc792eb63f57c07e513d94a72cc | |
| author | segher <segher@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Fri, 20 Jan 2017 01:22:27 +0000 (20 01:22 +0000) | ||
| committer | segher <segher@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Fri, 20 Jan 2017 01:22:27 +0000 (20 01:22 +0000) | ||
| tree | f98a91b994292cfbac91ec3a5421a13088238def | treesnapshot (tar.gz zip) |
| parent | eb5c0cb6c16d435f6797cd934ceaac73ac7db52c | commitdiff |
rs6000: Fix the new SSP guard configuration code (PR79140)
I foolishly tested this with r241087 reverted. After that revision
default_stack_protect_guard is no longer called if the compiler defaults
to using the TLS guard, which of course is the wrong thing to do if
there is some other way to enable the global guard.
This fixes it.
PR target/78875
PR target/79140
* config/rs6000/rs6000.c (TARGET_STACK_PROTECT_GUARD): Unconditionally
define to rs6000_init_stack_protect_guard.
(rs6000_init_stack_protect_guard): New function.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@244677 138bc75d-0d04-0410-961f-82ee72b054a4
I foolishly tested this with r241087 reverted. After that revision
default_stack_protect_guard is no longer called if the compiler defaults
to using the TLS guard, which of course is the wrong thing to do if
there is some other way to enable the global guard.
This fixes it.
PR target/78875
PR target/79140
* config/rs6000/rs6000.c (TARGET_STACK_PROTECT_GUARD): Unconditionally
define to rs6000_init_stack_protect_guard.
(rs6000_init_stack_protect_guard): New function.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@244677 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/ChangeLog | diffblobblamehistory | |
| gcc/config/rs6000/rs6000.c | diffblobblamehistory |