| 1 |
On 6/10/2005 12:16:07, Richard Freeman (rich@××××××××××××××.net) wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Daniel Gryniewicz wrote: |
| 6 |
> > |
| 7 |
> > The big reason would be because gcc 3.3.x (the stable compiler on x86) |
| 8 |
> > doesn't support it. It has a patch that adds the option to gcc, but it |
| 9 |
> > does nothing. Until x86 is on 3.4.x by default, you can't expect full |
| 10 |
> > support for stack-protector. |
| 11 |
> > |
| 12 |
> |
| 13 |
> I hadn't even realized that. And I thought that amd64 tended to lag |
| 14 |
> behind! As I recall 3.4 had quite a few benefits, as I normally don't |
| 15 |
> tend to run bleeding-edge... |
| 16 |
|
| 17 |
However Daniel's statement is false. ssp is included for x86 in gcc-3.3.x, and has been for a long time. You can't see it so easily on most 3.3.x versions as they're missing the definition of macros __SSP__ and __SSP_ALL__ but it's there nonetheless. |
| 18 |
|
| 19 |
SSP is currently not in any of the 4.0 versions; work is still ongoing there (SSP for 4.0 is back-ported from 4.1, where it will be included upstream). |
| 20 |
|
| 21 |
$ (cd /usr/portage/sys-devel/gcc; grep SSP_STABLE *ebuild) |
| 22 |
gcc-3.3.5-r1.ebuild:SSP_STABLE="x86 sparc amd64" |
| 23 |
gcc-3.3.5.20050130-r1.ebuild:SSP_STABLE="x86 sparc amd64" |
| 24 |
gcc-3.3.5.20050130-r2.ebuild:SSP_STABLE="x86 sparc amd64" |
| 25 |
gcc-3.3.6.ebuild:SSP_STABLE="x86 sparc amd64" |
| 26 |
gcc-3.4.3-r1.ebuild:SSP_STABLE="x86 sparc amd64 ppc ppc64" |
| 27 |
gcc-3.4.3.20050110-r2.ebuild:SSP_STABLE="x86 sparc amd64 ppc ppc64" |
| 28 |
gcc-3.4.4-r1.ebuild:SSP_STABLE="x86 sparc amd64 ppc ppc64" |
| 29 |
|
| 30 |
Kev. |
| 31 |
|
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
Archives