From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-64149-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id B0A9D138247
	for <garchives@archives.gentoo.org>; Thu,  9 Jan 2014 22:09:07 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id D7884E0BD0;
	Thu,  9 Jan 2014 22:09:03 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
	(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id E718AE0B8B
	for <gentoo-dev@lists.gentoo.org>; Thu,  9 Jan 2014 22:09:02 +0000 (UTC)
Received: from laptop1.gw.ume.nu (ip1-67.bon.riksnet.se [77.110.8.67])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	(Authenticated sender: zorry)
	by smtp.gentoo.org (Postfix) with ESMTPSA id B116633F1DA
	for <gentoo-dev@lists.gentoo.org>; Thu,  9 Jan 2014 22:09:01 +0000 (UTC)
From: Magnus Granberg <zorry@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] To enable ssp default in Gcc the toolchain.eclass need some changes.
Date: Thu, 09 Jan 2014 23:07:45 +0100
Message-ID: <1446166.mlyoc4zY7X@laptop1.gw.ume.nu>
Organization: Gentoo.org
User-Agent: KMail/4.11 (Linux/3.11.6-hardened-r2; KDE/4.11.0; x86_64; ; )
In-Reply-To: <1389304629.424.44.camel@belkin5>
References: <7554031.Sacz2dxc8i@laptop1.gw.ume.nu> <1389304629.424.44.camel@belkin5>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Archives-Salt: ffe82413-36d6-4aad-a4c6-8f96f61a6471
X-Archives-Hash: a02761bbca1f5ca561e788a2da19dbd0

torsdag 09 januari 2014 22.57.09 skrev  Pacho Ramos:
> El jue, 09-01-2014 a las 21:58 +0100, Magnus Granberg escribi=F3:
> > Hi
> >=20
> > Some time ago we discussed that we should enable stack smashing
> > (-fstack-protector) by default.  So we opened a bug to track this [=
1].
> > The affected Gcc version will be 4.8.2 and newer. Only amd64, x86, =
mips,
> > ppc, ppc64 and arm will be affected by this change.
> >=20
> > You can turn off ssp by using the nossp USE flag or by adding
> > -fno-stack-protector to the CFLAGS and/or CXXFLAGS. We are using th=
e same
> > patch as Debian/Ubuntu but with some Gentoo fixes.
> >=20
> > The patch will move the sed for the HARD_CFLAGS, ALLCFLAGS and
> > ALLCXXFLAGS from do_gcc_PIE_patches() to make_gcc_hard().  We will
> > make_gcc_hard() the default for all Gcc versions 4.8 and newer, and=
 turn
> > it on or off with hardened_gcc_works() that will make some sanity c=
hecks.
> >=20
> > /Magnus
>=20
> What are the advantages of disabling SSP to deserve that "special"
> handling via USE flag or easily disabling it appending the flag?
>=20
> Thanks a lot for the info :)

If you want Gcc not to build stuff with ssp as default you turn on the =
nossp=20
flag and rebuild Gcc.

/Magnus