public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: "H.J. Lu" <hjl@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. ac8cab1a9cd6fc200b0c1b624ac35df2239a910f Date: Fri, 11 Mar 2022 19:44:46 +0000 (GMT) [thread overview] Message-ID: <20220311194446.8AC653858D3C@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 ac8cab1a9cd6fc200b0c1b624ac35df2239a910f (commit) from 17fded72af297e476b63fb51e6a53cdd4efa3c30 (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 ac8cab1a9cd6fc200b0c1b624ac35df2239a910f Author: H.J. Lu <hjl.tools@gmail.com> Date: Sat Feb 12 06:38:22 2022 -0800 gcc-12: Mention -mno-direct-extern-access diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index a3e46eeb..9cff81b9 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -454,6 +454,10 @@ a work-in-progress.</p> <li>Add CS prefix to call and jmp to indirect thunk with branch target in r8-r15 registers via <code>-mindirect-branch-cs-prefix</code>. </li> + <li>Always use global offset table (GOT) to access external data and + function symbols when the new <code>-mno-direct-extern-access</code> + command-line option is specified. + </li> </ul> <!-- <h3 id="mips">MIPS</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-03-11 19:44 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=20220311194446.8AC653858D3C@sourceware.org \ --to=hjl@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).