public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 0f482d92ae32c99507ed0aa0961352f2ae5a6953 Date: Mon, 4 Jul 2022 08:57:58 +0000 (GMT) [thread overview] Message-ID: <20220704085758.4E0C83858C52@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 0f482d92ae32c99507ed0aa0961352f2ae5a6953 (commit) from c387e086bbcccce726babbea34f0befb6ca9b9bb (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 0f482d92ae32c99507ed0aa0961352f2ae5a6953 Author: Xi Ruoyao <xry111@xry111.site> Date: Mon Jul 4 14:59:53 2022 +0800 gcc-12/changes.html: document LoongArch -m{no-,}check-zero-division default change for 12.2 diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index ae03c3c6..ef957204 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -1027,6 +1027,32 @@ known to be fixed in the 12.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here).</p> +<!-- .................................................................. --> +<h2 id="12.2">GCC 12.2</h2> + +<p>Note: GCC 12.2 has not been released yet, so this section is a +work-in-progress.</p> + +<p>This is the <a href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=12.2">list +of problem reports (PRs)</a> from GCC's bug tracking system that are +known to be fixed in the 12.2 release. This list might not be +complete (that is, it is possible that some PRs that have been fixed +are not listed here).</p> + +<h3>Target Specific Changes</h3> + +<h4>LoongArch</h4> + +<ul> + <li> + <a id="loongarch-check-zero-div">The default setting of</a> + <code>-m[check|no-check]-zero-division</code> is changed for optimized + code. Now <code>-mno-check-zero-division</code> is the default for + all optimization levels but <code>-O0</code> and <code>-Og</code>. + The old behavior can be obtained by explicitly passing + <code>-mcheck-zero-division</code> to GCC. + </li> +</ul> <!-- .................................................................. --> </body> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-07-04 8: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=20220704085758.4E0C83858C52@sourceware.org \ --to=xry111@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).