Oh, my bad, sorry about the conflict marker.
I didn't realize the "Start of New Year" procedure until after I
googled it, sorry again.
-Han
rays. It's significantly more rare than the cases with arrays, but
these do need to be protected (for us).
-Han
On Fri, Dec 2, 2011 at 12:54 AM, Jakub Jelinek wrote:
>
> On Tue, Nov 29, 2011 at 03:53:50PM -0800, Han Shen(沈涵) wrote:
> > Hi, I propose to add to gcc a new option regarding sta
Hi, Joey, thanks!
The detail is here (should be included in my original post):
https://docs.google.com/a/google.com/document/d/1xXBH6rRZue4f296vGt9YQcuLVQHeE516stHwt8M9xyU/edit?hl=en_US
-Han
On Tue, Nov 29, 2011 at 10:44 PM, Ye Joey wrote:
> On Wed, Nov 30, 2011 at 7:53 AM, Han Shen
Hi, I propose to add to gcc a new option regarding stack protector -
"-fstack-protector-strong", in addition to current gcc's
"-fstack-protector-all", which protects ALL functions, and
"-fstack-protector", which protects functions that have a big
(signed/unsigned) char array or have alloca called.
