public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Kyrylo Tkachov <ktkachov@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e9db7dd717c5ddcb6c3fb35d1d57f2737fa8c5df Date: Thu, 30 Apr 2020 07:23:18 +0000 (GMT) [thread overview] Message-ID: <20200430072318.3BF8E3896811@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 e9db7dd717c5ddcb6c3fb35d1d57f2737fa8c5df (commit) from dfa292fab9e058d079b28973918beeec557b9ec6 (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 e9db7dd717c5ddcb6c3fb35d1d57f2737fa8c5df Author: Anton Youdkevitch <anton.youdkevitch@bell-sw.com> Date: Thu Apr 30 08:22:56 2020 +0100 wwwdocs: Added mentioning of TX3 chip to the list of the processors diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 41c2dc0d..6a273142 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -655,6 +655,7 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); <li>Arm Cortex-A65 (<code>cortex-a65</code>).</li> <li>Arm Cortex-A65AE (<code>cortex-a65ae</code>).</li> <li>Arm Cortex-A34 (<code>cortex-a34</code>).</li> + <li>Marvell ThunderX3 (<code>thunderx3t110</code>).</li> </ul> The GCC identifiers can be used as arguments to the <code>-mcpu</code> or <code>-mtune</code> options, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-04-30 7:23 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=20200430072318.3BF8E3896811@sourceware.org \ --to=ktkachov@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).