diff options
| author | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-04-24 17:36:02 +0100 |
|---|---|---|
| committer | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-04-30 13:08:13 +0100 |
| commit | 6ac83d350604c3e934d5e8a455ba7ec1c1c0240b (patch) | |
| tree | 8b9427647583160e8ccb026c6a5e718a070aa25a /gcc/tree.c | |
| parent | 852c4b04520d19d5a75e7f9ec5a5d980d5d1acc8 (diff) | |
| download | gcc-6ac83d350604c3e934d5e8a455ba7ec1c1c0240b.zip gcc-6ac83d350604c3e934d5e8a455ba7ec1c1c0240b.tar.gz gcc-6ac83d350604c3e934d5e8a455ba7ec1c1c0240b.tar.bz2 | |
aarch64: don't emit bti j after NOTE_INSN_DELETED_LABEL [PR94748]
It was previously discussed that indirect branches cannot go to
NOTE_INSN_DELETED_LABEL so inserting a landing pad is unnecessary.
See https://gcc.gnu.org/pipermail/gcc-patches/2019-May/522625.html
Before the patch a bti j was inserted after the label in
__attribute__((target("branch-protection=bti")))
int foo (void)
{
label:
return 0;
}
This is not necessary and weakens the security protection.
gcc/ChangeLog:
PR target/94748
* config/aarch64/aarch64-bti-insert.c (rest_of_insert_bti): Remove
the check for NOTE_INSN_DELETED_LABEL.
gcc/testsuite/ChangeLog:
PR target/94748
* gcc.target/aarch64/pr94748.c: New test.
Diffstat (limited to 'gcc/tree.c')
0 files changed, 0 insertions, 0 deletions