gcc-4.2.0 was (finally) released 5/13/07. I've renamed a 4.2.0 snapshot ebuild and am giving this a try. Reproducible: Always
this is more then an enhancement as it currently blocks full functionality options avaliable in the kernel.
Care to elaborate Bugs? I haven't seen any mention on the gcc mailing list....
(In reply to comment #2) > Care to elaborate Bugs? I haven't seen any mention on the gcc mailing list.... > ┌─── Enable -fstack-protector buffer overflow detection (EXPERIMENTAL) ───┐ │ CONFIG_CC_STACKPROTECTOR: │ │ │ │ This option turns on the -fstack-protector GCC feature. This │ │ feature puts, at the beginning of critical functions, a canary │ │ value on the stack just before the return address, and validates │ │ the value just before actually returning. Stack based buffer │ │ overflows (that need to overwrite this return address) now also │ │ overwrite the canary, which gets detected and the attack is then │ │ neutralized via a kernel panic. │ │ │ │ This feature requires gcc version 4.2 or above, or a distribution │ │ gcc with the feature backported. Older versions are automatically │ │ detected and for those versions, this configuration option is ignored. As 2.6.20 is stable for most archs, we are missing support for such a great feature in the kernel.
incorrect, our gcc has had SSP support for quite a long time
Hi Vapier, The bug should remain open since the original purpose was a 4.2.0 ebuild tracker, should it not?
your tree is out of date, there is a gcc-4.2.0 ebuild
Which tree would that be, don't see it in cvs: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/
then look again ... the webnodes arent updated instantaneously