public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 9963986ca53a121beb1902af3e4e2bb4d801bc3d Date: Sat, 1 Aug 2020 22:13:14 +0000 (GMT) [thread overview] Message-ID: <20200801221314.6A2CF3858D35@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 9963986ca53a121beb1902af3e4e2bb4d801bc3d (commit) from 7942aed93471fa7721e64a5669aa38b88198de80 (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 9963986ca53a121beb1902af3e4e2bb4d801bc3d Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Aug 2 00:12:26 2020 +0200 Update reference for PCOMMIT instruction deprecation. diff --git a/htdocs/gcc-6/changes.html b/htdocs/gcc-6/changes.html index 3713a394..e95aabbe 100644 --- a/htdocs/gcc-6/changes.html +++ b/htdocs/gcc-6/changes.html @@ -900,7 +900,7 @@ are not listed here).</p> <h3>IA-32/x86-64</h3> <ul> <li>Support for the <a - href="https://software.intel.com/en-us/blogs/2016/09/12/deprecate-pcommit-instruction">deprecated + href="https://software.intel.com/content/www/us/en/develop/blogs/deprecate-pcommit-instruction.html">deprecated pcommit instruction</a> has been removed.</li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-6/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-08-01 22:13 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=20200801221314.6A2CF3858D35@sourceware.org \ --to=gerald@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).