From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/
Date: Sat, 8 Jan 2022 03:49:22 +0000 (UTC) [thread overview]
Message-ID: <1641611567.e694058c76519b87a4bfda8ec6e8ea41f082323f.sam@gentoo> (raw)
commit: e694058c76519b87a4bfda8ec6e8ea41f082323f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 8 03:09:34 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 8 03:12:47 2022 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=e694058c
11.3.0: fix README.history
Signed-off-by: Sam James <sam <AT> gentoo.org>
11.3.0/gentoo/26_all_enable-cet.patch | 3 +--
11.3.0/gentoo/README.history | 11 ++++++++---
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/11.3.0/gentoo/26_all_enable-cet.patch b/11.3.0/gentoo/26_all_enable-cet.patch
index f6a1dce..38bb34a 100644
--- a/11.3.0/gentoo/26_all_enable-cet.patch
+++ b/11.3.0/gentoo/26_all_enable-cet.patch
@@ -5,8 +5,7 @@ Subject: [PATCH] Enable CET (-fcf-protection=full) by default
Needs:
- CET to be enabled for GCC
-- -DEXTRA_OPTIONS_CF to be passed during build (via toolchain.eclass)
- for now to avoid accidentally enabling it on other arches.
+- -DEXTRA_OPTIONS_CF to be passed during build (via toolchain.eclass).
Only supported on amd64.
diff --git a/11.3.0/gentoo/README.history b/11.3.0/gentoo/README.history
index 1faa3d6..bb83275 100644
--- a/11.3.0/gentoo/README.history
+++ b/11.3.0/gentoo/README.history
@@ -1,7 +1,13 @@
3 8 January 2022
- + 76_all_all_PR103910_12_ICE-on-PCH.patch
+ U 26_all_enable-cet.patch
-2 7 December 2021
+2 18 December 2021
+ + 75_all_x86_PR99703_12_no-cet-for-i486.patch
+
+1 7 December 2021
+ U 26_all_enable-cet.patch
+
+0 27 November 2021
+ 01_all_default-fortify-source.patch
+ 02_all_default-warn-format-security.patch
+ 03_all_default-warn-trampolines.patch
@@ -28,4 +34,3 @@
+ 24_all_lto-intl-workaround-PR95194.patch
+ 25_all_plugin-objdump.patch
+ 26_all_enable-cet.patch
- + 75_all_x86_PR99703_12_no-cet-for-i486.patch
next reply other threads:[~2022-01-08 3:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 3:49 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 2:14 [gentoo-commits] proj/gcc-patches:master commit in: 11.3.0/gentoo/ Sam James
2022-08-22 1:41 Sam James
2022-08-22 1:41 Sam James
2022-08-18 20:03 Sam James
2022-01-08 4:09 Sam James
2022-01-08 3:49 Sam James
2021-12-28 5:57 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-18 22:00 Sam James
2021-12-07 20:06 Sam James
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
2021-12-02 15:03 David Seifert
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=1641611567.e694058c76519b87a4bfda8ec6e8ea41f082323f.sam@gentoo \
--to=sam@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