public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: LuluCheng <chenglulu@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 907f21ff6915dda0b466c2236e8202602f72db18 Date: Wed, 19 Apr 2023 06:13:40 +0000 (GMT) [thread overview] Message-ID: <20230419061340.7FE67385841E@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 907f21ff6915dda0b466c2236e8202602f72db18 (commit) from 2d328ee7742306c8928e9bafc1c93493aa1bedb0 (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 907f21ff6915dda0b466c2236e8202602f72db18 Author: Lulu Cheng <chenglulu@loongson.cn> Date: Tue Apr 18 11:41:32 2023 +0800 gcc-13: Add changelog for LoongArch. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index f3b9afed..f6941534 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -563,6 +563,48 @@ a work-in-progress.</p> </li> </ul> +<h3 id="loongarch">LoongArch</h3> +<ul> + <li>New features + <ul> + <li>The new command-line option <code>-mexplicit-relocs</code> decides whether + to use the assembler relocation operator when dealing with symbolic addresses. + It is enabled by default if a compatible assembler (binutils 2.40 or later) + is present at GCC build time. + </li> + <li>The new command-line option <code>-mdirect-extern-access</code> can be used + to prevent accessing external symbols through GOT. + </li> + <li>The new variable attribute <a href="https://gcc.gnu.org/onlinedocs/gcc/LoongArch-Variable-Attributes.html#LoongArch-Variable-Attributes"><code>model</code></a> + has been added. + </li> + </ul> + </li> + <li>Built-in functions + <ul> + <li>The <code>rint</code> and <code>copysign</code> mathematical builtins + (and their float variants) are now implemented as inline LoongArch intrinsics. + </li> + <li>The <code>lrint</code>, <code>logb</code>, <code>scalbln</code>, + <code>scalbn</code> and <code>ldexp</code> mathematical builtins (and their + float variants) are now implemented as inline LoongArch intrinsics when using + <code>-fno-math-errno</code>. + </li> + <li>The <code>lceil</code> and <code>lfloor</code> mathematical builtins + (and their float variants) are now implemented as inline LoongArch intrinsics + when using <code>-ffp-int-builtin-inexact</code>. + </li> + </ul> + </li> + <li>Subprojects Support + <ul> + <li><code>libvtv</code> now supports LoongArch.</li> + <li><code>libitm</code> now supports LoongArch.</li> + <li>Address sanitizers other than HWASan and TSan are now supported on LoongArch.</li> + </ul> + </li> +</ul> + <!-- <h3 id="mips">MIPS</h3> --> <!-- <h3 id="mep">MeP</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-04-19 6: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=20230419061340.7FE67385841E@sourceware.org \ --to=chenglulu@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).