From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 8.2.0/gentoo/
Date: Sun, 10 Feb 2019 12:12:37 +0000 (UTC) [thread overview]
Message-ID: <1549800501.1fe872f729f1361ee45fb0792ca4194cf9c1caeb.slyfox@gentoo> (raw)
commit: 1fe872f729f1361ee45fb0792ca4194cf9c1caeb
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 10 12:08:21 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sun Feb 10 12:08:21 2019 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=1fe872f7
8.2.0: don't enable -fstack-clach-protection by default
In bug #675050 I noticed that -fstack-clash-protection is enabled
not just for hardened users but for USE=ssp users as well.
That was not an intention of the patch. The change enables
-fstack-clach-protection only for -DEXTRA_OPTIONS (hardened users).
See https://bugs.gentoo.org/675050 for longer-term plans to
enable -fstack-clach-protection for more users.
Bug: https://bugs.gentoo.org/675050
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
| 2 +-
8.2.0/gentoo/README.history | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--git a/8.2.0/gentoo/55_all_extra-options.patch b/8.2.0/gentoo/55_all_extra-options.patch
index 3e8275f..9187af8 100644
--- a/8.2.0/gentoo/55_all_extra-options.patch
+++ b/8.2.0/gentoo/55_all_extra-options.patch
@@ -19,7 +19,7 @@ On Hardened we add some options like -fstack-clash-protection and -z now
+/* Default value for flag_clash_protector when flag_clash_protector is
+ initialized to -1. */
-+#ifdef ENABLE_ESP
++#ifdef EXTRA_OPTIONS
+#define DEFAULT_FLAG_SCP 1
+#endif
+#ifndef DEFAULT_FLAG_SCP
diff --git a/8.2.0/gentoo/README.history b/8.2.0/gentoo/README.history
index a20d870..bf28171 100644
--- a/8.2.0/gentoo/README.history
+++ b/8.2.0/gentoo/README.history
@@ -1,5 +1,6 @@
1.8 TODO
+ 116_all_ipa-pgo-PR88561-fix.patch
+ U 55_all_extra-options.patch
1.7 26 Dec 2018
+ 114_all_kr-decl-PR88214.patch
next reply other threads:[~2019-02-10 12:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 12:12 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-08 22:42 [gentoo-commits] proj/gcc-patches:master commit in: 8.2.0/gentoo/ Sergei Trofimovich
2019-02-11 21:59 Sergei Trofimovich
2019-01-29 20:24 Sergei Trofimovich
2018-12-26 19:31 Sergei Trofimovich
2018-12-18 22:38 Sergei Trofimovich
2018-12-10 22:48 Sergei Trofimovich
2018-12-01 13:06 Sergei Trofimovich
2018-11-22 23:55 Sergei Trofimovich
2018-10-27 9:04 Sergei Trofimovich
2018-10-21 9:24 Sergei Trofimovich
2018-10-20 9:40 Sergei Trofimovich
2018-10-18 20:40 Sergei Trofimovich
2018-10-08 22:05 Sergei Trofimovich
2018-10-08 22:05 Sergei Trofimovich
2018-10-01 6:41 Sergei Trofimovich
2018-09-30 22:08 Sergei Trofimovich
2018-09-23 20:37 Sergei Trofimovich
2018-09-15 19:30 Sergei Trofimovich
2018-08-12 22:56 Sergei Trofimovich
2018-08-12 20:27 Sergei Trofimovich
2018-08-08 8:37 Sergei Trofimovich
2018-08-08 8:31 Sergei Trofimovich
2018-08-08 8:26 Sergei Trofimovich
2018-08-08 7:58 Sergei Trofimovich
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=1549800501.1fe872f729f1361ee45fb0792ca4194cf9c1caeb.slyfox@gentoo \
--to=slyfox@gentoo.org \
--cc=gentoo-commits@lists.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