public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 79b804a9bda634f0efad4fe15564d1b2374adb35 Date: Wed, 20 Dec 2023 07:59:31 +0000 (GMT) [thread overview] Message-ID: <20231220075931.E4C2B386180D@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 79b804a9bda634f0efad4fe15564d1b2374adb35 (commit) from e56dc0003729ea6f7d26594dae34d218543edb49 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 79b804a9bda634f0efad4fe15564d1b2374adb35 Author: Alexandre Oliva <oliva@adacore.com> Date: Wed Dec 20 04:57:24 2023 -0300 new AdaCore-contributed hardening features in gcc 13 and 14 Mention hardening of conditionals (added in gcc 13), control flow redundancy, hardened booleans, and stack scrubbing. Also cover forced inlining of string operations while at that. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index ee6383a0..d3bacc16 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -168,6 +168,12 @@ You may also want to check out our been added, see also <a href="https://gcc.gnu.org/onlinedocs/gcc/Freestanding-Environments.html">Profiling and Test Coverage in Freestanding Environments</a>. </li> + <li> + New options <code>-fharden-compares</code> + and <code>-fharden-conditional-branches</code> to verify compares + and conditional branches, to detect some power-deprivation + hardware attacks, using reversed conditions. + </li> </ul> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 11c7ca7e..24e6409a 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -128,6 +128,35 @@ a work-in-progress.</p> of hardening flags. The options it enables can be displayed using the <code>--help=hardened</code> option. </li> + <li> + New option <code>-fharden-control-flow-redundancy</code>, to + verify, at the end of functions, that the visited basic blocks + correspond to a legitimate execution path, so as to detect and + prevent attacks that transfer control into the middle of + functions. + </li> + <li> + New type attribute <code>hardbool</code>, for C and Ada. Hardened + booleans take user-specified representations for <code>true</code> + and <code>false</code>, presumably with higher hamming distance + than standard booleans, and get verified at every use, detecting + memory corruption and some malicious attacks. + </li> + <li> + New type attribute <code>strub</code> to control stack scrubbing + properties of functions and variables. The stack frame used by + functions marked with the attribute gets zeroed-out upon returning + or exception escaping. Scalar variables marked with the attribute + cause functions contaning or accessing them to get stack scrubbing + enabled implicitly. + </li> + <li> + New option <code>-finline-stringops</code>, to force inline + expansion of <code>memcmp</code>, <code>memcpy</code>, + <code>memmove</code> and <code>memset</code>, even when that is + not an optimization, to avoid relying on library + implementations. + </li> </ul> <!-- .................................................................. --> <h2 id="languages">New Languages and Language specific improvements</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 6 ++++++ htdocs/gcc-14/changes.html | 29 +++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-12-20 7:59 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231220075931.E4C2B386180D@sourceware.org \ --to=aoliva@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).