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. 97390ada23198cb3849b75a17735d582919cfc46 Date: Sun, 13 Jun 2021 05:57:30 +0000 (GMT) [thread overview] Message-ID: <20210613055730.7714B3857414@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 97390ada23198cb3849b75a17735d582919cfc46 (commit) from 58d2cdf688b58f460e9694abbd3de2442542d41f (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 97390ada23198cb3849b75a17735d582919cfc46 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Sun Jun 13 07:55:37 2021 +0200 gcc-11/changes.html: Editorial changes for RISC-V diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 97606174..491b6b71 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -953,33 +953,36 @@ You may also want to check out our <ul> <li>Support address sanitizer for RISC-V.</li> <li>Support big-endian for RISC-V, thanks to Marcus Comstedt.</li> - <li>Implement new style of architecture extension test macros, - each architecture extension has corresponding feature test macro, which - could use to test its existence and version information. + <li>Implement new style of architecture extension test macros: + each architecture extension has a corresponding feature test macro, + which can be used to test its existence and version information. </li> - <li>Legacy architecture extension test macro like <code>__riscv_atomic</code>, - are deprecated, but it will still supported for at least 2 release cycles. + <li>Legacy architecture extension test macros like + <code>__riscv_atomic</code> are deprecated, but will still be + supported for at least 2 release cycles. </li> <li>Support IFUNC for <code>riscv*-*-linux*</code>.</li> - <li>Add new option -misa-spec=* to control ISA spec version, default is 2.2, - this option could control the default version of each extensions.</li> - <li>Introduce <code>--with-multilib-generator</code> to configure time option, - this option could flexible config multi-lib settings, syntax is same as - RISC-V's <code>multilib-generator</code>. + <li>Add new option <code>-misa-spec=*</code> to control ISA spec version. + This controls the default version of each extensions. + It defaults to 2.2.</li> + <li>Introduce the <code>--with-multilib-generator</code> configure time + option. + This allows for flexible config multi-lib settings. Its syntax is + the same as RISC-V's <code>multilib-generator</code>. </li> <li>Extend the sytax for <code>multilib-generator</code>, support expansion operator <code>*</code> to reduce the complexity of complicated multi-lib - re-use rule. + re-use rules. </li> - <li>Support <code>-mcpu=*</code> option, the behavior is aligned to RISC-V - clang/LLVM, it will set pipeline model and architecture extension, like + <li>Support <code>-mcpu=*</code> option aligned with RISC-V clang/LLVM. + It sets the pipeline model and architecture extensions, like <code>-mtune=*</code> plus <code>-march=*</code>. </li> <li>Support for TLS stack protector canary access, thanks to Cooper Qu. </li> <li>Support <code>__builtin_thread_pointer</code> for RISC-V.</li> - <li>Introduce <code>shorten_memrefs</code> optimization, which could reduce the - code size for memory access, thanks to Craig Blackmore. + <li>Introduce <code>shorten_memrefs</code> optimization, which reduces + the code size for memory access, thanks to Craig Blackmore. </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 33 ++++++++++++++++++--------------- 1 file changed, 18 insertions(+), 15 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-06-13 5:57 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=20210613055730.7714B3857414@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).