From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH] To enable ssp default in Gcc the toolchain.eclass need some changes.
Date: Thu, 9 Jan 2014 17:26:03 -0600 [thread overview]
Message-ID: <20140109172603.659c630f@caribou.gateway.pace.com> (raw)
In-Reply-To: 52CF1080.7010400@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Thu, 09 Jan 2014 16:11:28 -0500
"Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/09/2014 03:58 PM, Magnus Granberg wrote:
> > Hi
> >
> > 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.
> >
> > 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 the same
> > patch as Debian/Ubuntu but with some Gentoo fixes.
>
> Please avoid "noblah" use flags.
>
> http://devmanual.gentoo.org/general-concepts/use-flags/
>
> ssp flag that defaults to on is fine.
This flag already exists and has always worked this way. We don't have USE
defaults yet.
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-09 23:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 20:58 [gentoo-dev] [PATCH] To enable ssp default in Gcc the toolchain.eclass need some changes Magnus Granberg
2014-01-09 21:11 ` Rick "Zero_Chaos" Farina
2014-01-09 22:19 ` William Hubbs
2014-01-09 23:26 ` Ryan Hill [this message]
2014-01-09 23:30 ` [gentoo-dev] " Andreas K. Huettel
2014-01-09 23:41 ` William Hubbs
2014-01-10 0:12 ` Ryan Hill
2014-01-10 6:35 ` Rick "Zero_Chaos" Farina
2014-01-10 15:50 ` Ryan Hill
2014-01-10 18:37 ` Rick "Zero_Chaos" Farina
2014-01-10 20:08 ` Anthony G. Basile
2014-01-10 21:56 ` Ryan Hill
2014-01-09 21:57 ` [gentoo-dev] " Pacho Ramos
2014-01-09 22:06 ` Anthony G. Basile
2014-01-09 22:16 ` Pacho Ramos
2014-01-09 22:21 ` Michał Górny
2014-01-09 22:29 ` Rick "Zero_Chaos" Farina
2014-01-09 23:03 ` Anthony G. Basile
2014-01-09 23:09 ` Anthony G. Basile
2014-01-09 23:19 ` Rick "Zero_Chaos" Farina
2014-01-09 23:30 ` [gentoo-dev] " Ryan Hill
2014-01-10 0:17 ` Ryan Hill
2014-01-10 6:39 ` Rick "Zero_Chaos" Farina
2014-01-09 23:59 ` [gentoo-dev] " Rich Freeman
2014-01-10 4:50 ` Michał Górny
2014-01-09 23:01 ` Anthony G. Basile
2014-01-09 23:13 ` Rick "Zero_Chaos" Farina
2014-01-09 23:28 ` Anthony G. Basile
2014-01-09 22:07 ` Magnus Granberg
2014-01-09 23:56 ` [gentoo-dev] " Ryan Hill
2014-01-10 15:45 ` Magnus Granberg
2014-01-10 5:18 ` Ryan Hill
2014-01-10 15:24 ` Magnus Granberg
2014-01-10 16:30 ` Ryan Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140109172603.659c630f@caribou.gateway.pace.com \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox