public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Jambor <jamborm@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 535e392dde5954ea7c40dd88952d775f38b74000 Date: Mon, 22 Nov 2021 14:14:42 +0000 (GMT) [thread overview] Message-ID: <20211122141442.9F162385840F@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 535e392dde5954ea7c40dd88952d775f38b74000 (commit) from 624ac352eb45ca54c934dcdc44f157f591e67122 (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 535e392dde5954ea7c40dd88952d775f38b74000 Author: Martin Jambor <mjambor@suse.cz> Date: Mon Nov 22 15:13:17 2021 +0100 gcc-12/changes.html: Document that Ofast means -fno-semantic-interposition diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 43fc5bc0..2f80b34a 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -72,6 +72,9 @@ a work-in-progress.</p> be removed in the next release. All ports now default to emit DWARF (version 2 or later) debugging info or are obsoleted. </li> + <li>The optimization level <code>-Ofast</code> now implies + <code>-fno-semantic-interposition</code>. + </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-11-22 14:14 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=20211122141442.9F162385840F@sourceware.org \ --to=jamborm@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).