v2: The GNU C Library 2.16 release plan

[Carlos O'Donell]

On 6/4/2012 1:53 PM, Roland McGrath wrote:
>> Is there any way we can come to better consensus around the fortify warnings?
> 
> What seems appropriate for configurations that want to enable fortification
> by default is that they predefine some other macro whose meaning is "set
> _FORTIFY_SOURCE if optimizing", rather than predefining _FORTIFY_SOURCE
> itself.  That way the features.h check can distinguish a user adding
> -D_FORTIFY_SOURCE without -O from the predefinition.

So what's the next step?

* Configurations agree to _FORTIFY_SOURCE_IF_OPT?
  - Who would set this and where?
* We change glibc to use _FORTIFY_SOURCE_IF_OPT?

Cheers,
Carlos.
-- 
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026