https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
Kangjie Lu changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
Kangjie Lu changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
--- Comment #9 from Kangjie Lu ---
(In reply to Andrew Pinski from comment #8)
> A simple google search (secure memset [glibc]) finds a few things:
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1381.pdf
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
--- Comment #7 from Kangjie Lu ---
(In reply to Andrew Pinski from comment #6)
> >More information can be found in our research paper:
> >http://www.cc.gatech.edu/~klu38/publications/unisan-ccs16.pdf
>
>
> You research paper is wrong and does
: critical
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: kjlu at gatech dot edu
Target Milestone: ---
Created attachment 39817
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39817=edit
testcase
Hello,
I'd like to rep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
--- Comment #12 from Kangjie Lu ---
(In reply to Andreas Schwab from comment #11)
> The problem with that strategy is that padding is architecture dependent,
> and care must be taken not to introduce ABI breakage.
Agreed. Or a developer will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
--- Comment #13 from Kangjie Lu ---
(In reply to jos...@codesourcery.com from comment #10)
> If you care about information in bytes that are not part of a field with
> other semantic significance, you should use -Werror=padded to get errors
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77992
--- Comment #15 from Kangjie Lu ---
(In reply to Richard Biener from comment #14)
> Re-opening as an enhacement request for sth like -fexplict-padding adding
> artificial fields to structures padding.
>
> Patches welcome (hint: look into
