[wwwdocs] gcc-12/changes.html: document LoongArch -m{no-,}check-zero-division default change for 12.2

Message ID 84f4760821fd274af517f28aa0ae122ef426dbb9.camel@xry111.site
State New
Headers
Series [wwwdocs] gcc-12/changes.html: document LoongArch -m{no-,}check-zero-division default change for 12.2 |

Commit Message

Xi Ruoyao July 4, 2022, 7:11 a.m. UTC
  Document a behavior change in r12-8546.  Ok for wwwdocs?

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

Comments

Richard Biener July 4, 2022, 8:15 a.m. UTC | #1
On Mon, Jul 4, 2022 at 9:12 AM Xi Ruoyao <xry111@xry111.site> wrote:
>
> Document a behavior change in r12-8546.  Ok for wwwdocs?

OK.

> ---
>  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
>
>
  
Gerald Pfeifer July 5, 2022, 11:01 a.m. UTC | #2
On Mon, 4 Jul 2022, Xi Ruoyao wrote:
> Document a behavior change in r12-8546.  Ok for wwwdocs?

Thanks also for including the GCC 12.2 bug query as part of this. :)

Gerald
  

Patch

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>