[Bug target/96191] aarch64 stack_protect_test canary leak

2020-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #10 from CVS Commits --- The releases/gcc-8 branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:3ee527923b1ce92c6b16c587d072720a6c813c95 commit r8-10627-g3ee527923b1ce92c6b16c587d072720a6c813c95 Author: Richard Sand

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-07 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #9 from CVS Commits --- The releases/gcc-9 branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:3e40be9cc92d3fa117be7f4fab07cedeed8361a2 commit r9-8795-g3e40be9cc92d3fa117be7f4fab07cedeed8361a2 Author: Richard Sandif

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-07 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #8 from CVS Commits --- The releases/gcc-9 branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:5380912a17ea09a8996720fb62b1a70c16c8f9f2 commit r9-8794-g5380912a17ea09a8996720fb62b1a70c16c8f9f2 Author: Richard Sandif

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-07 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #7 from CVS Commits --- The releases/gcc-10 branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:8f6b7c9796035ad8b2cdfbce5d3d11dd4b81fad7 commit r10-8584-g8f6b7c9796035ad8b2cdfbce5d3d11dd4b81fad7 Author: Richard Sand

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-07 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #6 from CVS Commits --- The releases/gcc-10 branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:bab5fdaf9abb1236a7a56258d1d36265068b4827 commit r10-8583-gbab5fdaf9abb1236a7a56258d1d36265068b4827 Author: Richard Sand

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-06 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #5 from CVS Commits --- The master branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:6a3f3e08723063ea2dadb7ddf503f02972a724e2 commit r11-2598-g6a3f3e08723063ea2dadb7ddf503f02972a724e2 Author: Richard Sandiford Da

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-08-05 Thread cvs-commit at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #4 from CVS Commits --- The master branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:fe1a26429038d7cd17abc53f96a6f3e2639b605f commit r11-2576-gfe1a26429038d7cd17abc53f96a6f3e2639b605f Author: Richard Sandiford Da

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-07-14 Thread wilson at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 --- Comment #3 from Jim Wilson --- The location of the canary is not known to the attacker. You are not supposed to leak the address of the canary or the value of the canary. If you leak either, then an attacker has a chance to restore the cana

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-07-14 Thread wilco at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 Wilco changed: What|Removed |Added CC||wilco at gcc dot gnu.org --- Comment #2 from Wil

[Bug target/96191] aarch64 stack_protect_test canary leak

2020-07-14 Thread rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191 rsandifo at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot