-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/10/2014 10:50 AM, Ryan Hill wrote: > On Fri, 10 Jan 2014 01:35:09 -0500 > "Rick \"Zero_Chaos\" Farina" <zeroch...@gentoo.org> wrote: > >> More to the point, "this specific use flag" appears to have no purpose >> what-so-ever. If a user can do exactly the same with >> CFLAGS=-fno-stack-protector in make.conf, and it would be INSANE for a >> package to dep on gcc[nossp] then this is has got to be one of the most >> useless use flags in gentoo. > > Having slept on it I'm starting to agree. My first argument was that on > hardened ssp is -fstack-protector-all, which is much more expensive, and it > adds -fstack-check and -z,now to the linker by default as well. The pie half > adds -fPIE but also a crtbeginP section for linking static libs with -pie. So > there are situations where you want to disable one or both, if only for > testing. But what I forgot is that hardened installs multiple gcc-config > profiles to switch these out on the fly. So there goes that idea. > > It might be useful to have these flags so we can mask them on archs that don't > support ssp/pie. But that's always been true and it looks like sh is the only > place we've bothered for some reason. > >> Not saying I would block this patch, not saying it has to be this >> second, but I see this use flag as a small example of things in >> toolchain which could probably be cleaned up if fresh eyes were to see >> things. > > Yes, and believe it or not I appreciate the input. I know I'm stubborn as > hell > but eventually common sense gets through.
Well, that's why I asked for your opinion ;-) Now since I know you have plenty to do I'll leave you with this though bouncing around in there. When you are working on your updates, we would prefer that this "nopie" and "nossp" flags to bye bye. If you REALLY wanted a way to change the gcc profile then do for the normal users what the hardened team does and offer them multiple profiles. Obviously we should involved docs team at that point, but it makes much more sense to "gcc-config 3" than rebuild gcc with a different use flag. Again, doesn't have to be this second, but I want it in your head since I know you are working on this stuff right now. Thanks! Zero > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS0D3YAAoJEKXdFCfdEflK1HEP/jdF9nwxpDde8j4PMypeZSm8 FKG0l3MmMr6+2joKkgZSLqVebiTcc8OtCgpk6UJJVEWSpNMWqrjqX5oTkIBAJisr sGUVGJEAyDCCsNJwTtbW/sBKw5r5Xh1zLk92T55YhaWBMTJPc4UzSqhpr+TBZ8wJ T77XOIPtxOdZYjubGqIm4lSWsgT/o0F0S6kge75iYm81omuBtZpAze6ePE2DteTj IinauiMUhqkTYXv6AXdBNv4dDLiInyDrdlUIFbWlawxsx64Wpt77j3jA2fHrRmEf 8MPvoRzLpX/7DPMDaS3WyGBVpM8CPNTaxQiXjC+giXNj4jkJyop/m6Q4a00wYvQg C+1o6JMEsYNlrIuSooInFxQ5OqARzna4lFc7Jp6+eMaBE4NhYkPkxJ7KOerD3IvI yW1lSN5gte/zxgm3Ny/96Zw/6+Jx5ffQNc8bCgE2+TxDG0wwB5qZGn/w6dl6gFYX jXD5dFmw3C5T2HhTIZ6j9n8b0MNkT71CzFA2O4EzEyPrI3b8KTmU6PkppT/Vwlo4 EHc/EUWdjSCPH/FzzJdcNbFUdvLCigZQqvaggN3Qjh/YyJRECXz6Hy2M8VTOg18a XVE36Z5/DNeobeBQ5XaKLcb5po22wJueJzKFdEK+GaSewzn+FXsNCquVZV9Y3lZC epKNxmbxtX/Uqx8q9+74 =++P6 -----END PGP SIGNATURE-----
