[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2022-09-27 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #13 from CVS Commits --- The master branch has been updated by H.J. Lu : https://gcc.gnu.org/g:a25982ada523689c8745d7fb4b1b93c8f5dab2e7 commit r13-2909-ga25982ada523689c8745d7fb4b1b93c8f5dab2e7 Author: H.J. Lu Date: Thu Jul 14

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2022-07-13 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2022-07-13 Thread hjl.tools at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #12 from H.J. Lu --- Created attachment 53294 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53294=edit A patch Something like this?

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2022-07-13 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 Andrew Pinski changed: What|Removed |Added CC||hjl.tools at gmail dot com --- Comment

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2018-10-18 Thread bugdal at aerifal dot cx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #10 from Rich Felker --- Since musl 1.1 introduced unconditional setup of thread pointer, the previously-reported consequence is no longer relevant with modern versions. However it's still either a missed optimization (emitting

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2014-02-16 Thread jackie.rosen at hushmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 Jackie Rosen jackie.rosen at hushmail dot com changed: What|Removed |Added CC|

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2014-01-15 Thread basile at opensource dot dyc.edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 Anthony G. Basile basile at opensource dot dyc.edu changed: What|Removed |Added CC|

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-10-01 Thread timo.teras at iki dot fi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #5 from Timo Teräs timo.teras at iki dot fi --- I have the same issue and confirm this issue. Any ideas how to fix it properly?

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-10-01 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added CC||jakub at gcc dot

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-10-01 Thread bugdal at aerifal dot cx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #7 from Rich Felker bugdal at aerifal dot cx --- I claim it's a bug in that GCC should _either_ check the canary at some point, or eliminate the code that's loading the canary to begin with since it will never be checked.

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-08-28 Thread rose.garcia-eggl2fk at yopmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 Rose Garcia rose.garcia-eggl2fk at yopmail dot com changed: What|Removed |Added CC|

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-08-26 Thread bugdal at aerifal dot cx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #1 from Rich Felker bugdal at aerifal dot cx --- One more thing: I would be happy with either of two solutions, either: (1) Checking the canary before calling a noreturn function, just like performing a check before a tail-call, or

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-08-26 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org --- The best solution: Don't use the same triplet as the GNU (glibc) one. Have musl have its own triplet.

[Bug middle-end/58245] -fstack-protector[-all] does not protect functions that call noreturn functions

2013-08-26 Thread bugdal at aerifal dot cx
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58245 --- Comment #3 from Rich Felker bugdal at aerifal dot cx --- We already do that; the patch is in the musl-cross repo here: https://bitbucket.org/GregorR/musl-cross or https://github.com/GregorR/musl-cross However, we want the stack-protector