public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	Richard Biener <richard.guenther@gmail.com>,
	Chenghua Xu <xuchenghua@loongson.cn>,
	Weining Lu <luweining@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: [PATCH][wwwdocs] gcc-12/changes.html: document LoongArch -m{no-,}check-zero-division default change for 12.2
Date: Mon, 04 Jul 2022 15:11:53 +0800	[thread overview]
Message-ID: <84f4760821fd274af517f28aa0ae122ef426dbb9.camel@xry111.site> (raw)

Document a behavior change in r12-8546.  Ok for wwwdocs?

---
 htdocs/gcc-12/changes.html | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

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&amp;resolution=FIXED&amp;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>
-- 
2.37.0



             reply	other threads:[~2022-07-04  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  7:11 Xi Ruoyao [this message]
2022-07-04  8:15 ` Richard Biener
2022-07-05 11:01 ` Gerald Pfeifer

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=84f4760821fd274af517f28aa0ae122ef426dbb9.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=i@xen0n.name \
    --cc=luweining@loongson.cn \
    --cc=richard.guenther@gmail.com \
    --cc=xuchenghua@loongson.cn \
    /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: link
Be 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).