[Bug middle-end/69976] Zero the local stack on function exit

2023-05-16 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #14 from Andrew Pinski --- There is an option now to zero out the call used registers: https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Optimize-Options.html#index-fzero-call-used-regs But there is not one for zeroing of arrays.

[Bug middle-end/69976] Zero the local stack on function exit

2021-05-04 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug middle-end/69976] Zero the local stack on function exit

2017-10-24 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #13 from David Malcolm --- Did this patch ever get posted to gcc-patc...@gcc.gnu.org? That's probably the best way to get some traction on this. Note that feature-freeze for GCC 8 is coming in the next few weeks, AIUI.

[Bug middle-end/69976] Zero the local stack on function exit

2017-10-21 Thread gnu at pureftpd dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 Frank Denis changed: What|Removed |Added CC||gnu at pureftpd dot org --- Comment #12 fr

[Bug middle-end/69976] Zero the local stack on function exit

2016-09-28 Thread daniel.gutson at intel dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #11 from Daniel Gutson --- Any update on this?

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-15 Thread marcos.diaz at tallertechnologies dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #10 from Marcos Diaz --- Thanks for the test, we forgot to append some test too. It worked ok. if you want you can apply that patch in gcc 5.2.0.

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-15 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #9 from David Malcolm --- Created attachment 37972 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37972&action=edit Crude test case In case it's helpful, here's a crude attempt at a black-box test case for this: read a secret i

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-15 Thread marcos.diaz at tallertechnologies dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #8 from Marcos Diaz --- Created attachment 37971 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37971&action=edit An implementation for x86 security_sensitive function attribute Hi, we made this patch, that adds an attribute 's

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #7 from David Malcolm --- (In reply to Jakub Jelinek from comment #6) > But even if you clear the sensitive data from the stack array, it might > still live in the registers from which you stored the sensitive data into > that array e

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-04 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #6 from Jakub Jelinek --- (In reply to David Malcolm from comment #5) > From a user's perspective, would this be better as a property of the data > (or of its *type*), rather than of the function? i.e. have the user mark > the on-sta

[Bug middle-end/69976] Zero the local stack on function exit

2016-03-04 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment

[Bug middle-end/69976] Zero the local stack on function exit

2016-02-26 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #4 from joseph at codesourcery dot com --- I think you should read the discussion starting at and see how your ideas compare to it, then maybe try to restart that discussion and get

[Bug middle-end/69976] Zero the local stack on function exit

2016-02-26 Thread daniel.gutson at tallertechnologies dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 --- Comment #3 from Daniel Gutson --- Those are very good ideas but fell into the land of the backend. The red zone IIUC is a x86_64 only ABI concept. What do you think about adding also a -m counterpart option with the same semantic but for the

[Bug middle-end/69976] Zero the local stack on function exit

2016-02-26 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug middle-end/69976] Zero the local stack on function exit

2016-02-26 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69976 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|