On Wed, Nov 16, 2005 at 10:32:45PM +0100, Peter S. Mazinger wrote: > what happens w/ -fstack-protector-all -fstack-protector (in this order) ? > do we have (2) or (1)
We have 1. > so now it does > -fstack-protector #define __SSP__ 1 ; #undef __SSP_ALL__ > -fstack-protector-all #define __SSP_ALL__ 2 ; #undef __SSP__ > > and the last wins. I don't know what you're looking at, but it isn't mainline. The defines are not controled this way. r~
