On Sat, Jan 12, 2019 at 12:57 PM 隆春 <longchun...@alibaba-inc.com> wrote: > > commit（2a61f4747eeaa85ce26ca9fbd81421b15facd018）rename CC_STACKPROTECTOR_NONE > config. but unfortunately if the compiler support option -fno-stack-protector, > CC_HAS_STACKPROTECTOR_NONE will not be disabled.
You completely misunderstood that commit. The meaning of CC_HAS_STACKPROTECTOR_NONE is "the compiler recognizes -fno-stack-protector option" instead of "disable the stack protector". Now that STACKPROTECTOR is a boolean option, CONFIG_STACKPROTECTOR=n means "disable the stack protector". > CC_HAS_STACKPROTECTOR_NONE and CC_STACKPROTECTOR_STRONG will be enabled at > once, > as the following conditions: > 1. gcc support -fno-stack-protector & -fstack-protector-strong > 2. enabled CC_STACKPROTECTOR_STRONG & STACKPROTECTOR CC_STACKPROTECTOR_STRONG does not exist any more. STACKPROTECTOR_STRONG and STACKPROTECTOR exist. > 3. disabled CC_HAS_STACKPROTECTOR_NONE This represents the compiler capability. Not a user-configurable option. > > > -- Best Regards Masahiro Yamada
