public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f065d2cfe7429033ac87adbfdfae43875fbac2ab
Date: Fri,  1 Apr 2022 14:29:57 +0000 (GMT)	[thread overview]
Message-ID: <20220401142958.029053858D28@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  f065d2cfe7429033ac87adbfdfae43875fbac2ab (commit)
       via  f370b62b8dae4d0ec11a957f5c3817039aca3958 (commit)
      from  3be1a28f58d6063258407b0751e8fb55df4749c8 (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 f065d2cfe7429033ac87adbfdfae43875fbac2ab
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Fri Apr 1 09:35:15 2022 -0400

    gcc-12: linkify various options

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index ed555e31..4e1f6b0f 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -197,17 +197,20 @@ a work-in-progress.</p>
       the clang language extension was added.</li>
   <li>New warnings:
     <ul>
-      <li><code>-Wbidi-chars</code> warns about potentially misleading UTF-8
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wbidi-chars"><code>-Wbidi-chars</code></a>
+	warns about potentially misleading UTF-8
 	bidirectional control characters.  The default is
 	<code>-Wbidi-chars=unpaired</code>
 	(<a href="https://gcc.gnu.org/PR103026">PR103026</a>)</li>
-      <li><code>-Warray-compare</code> warns about comparisons between two operands of
-	  array type (<a href="https://gcc.gnu.org/PR97573">PR97573</a>)</li>
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Warray-compare"><code>-Warray-compare</code></a>
+	warns about comparisons between two operands of
+	array type (<a href="https://gcc.gnu.org/PR97573">PR97573</a>)</li>
     </ul>
   </li>
   <li>Enhancements to existing warnings:
     <ul>
-      <li><code>-Wattributes</code> has been extended so that it's
+      <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wattributes"><code>-Wattributes</code></a>
+	has been extended so that it's
 	possible to use <code>-Wno-attributes=ns::attr</code> or
 	<code>-Wno-attributes=ns::</code> to suppress warnings about unknown scoped
 	attributes (in C++11 and C2X).  Similarly,
@@ -233,7 +236,8 @@ a work-in-progress.</p>
     <li>The <code>#elifdef</code> and <code>#elifndef</code>
     preprocessing directives are now supported.</li>
     <li>The <code>printf</code> and <code>scanf</code> format checking
-    with <code>-Wformat</code> now supports the <code>%b</code> format
+      with <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wformat"><code>-Wformat</code></a>
+      now supports the <code>%b</code> format
     specified by C2X for binary integers, and the <code>%B</code>
     format recommended by C2X for <code>printf</code>.
   </ul></li>
@@ -288,10 +292,12 @@ a work-in-progress.</p>
       (<a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=87c2080b">git</a>)</li>
   <li>Deduction guides can be declared at class scope
       (<a href="https://gcc.gnu.org/PR79501">PR79501</a>)</li>
-  <li><code>-Wuninitialized</code> warns about using uninitialized variables in
+  <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wuninitialized"><code>-Wuninitialized</code></a>
+    warns about using uninitialized variables in
       member initializer lists (<a href="https://gcc.gnu.org/PR19808">PR19808</a>)
       </li>
-  <li><code>-Wint-in-bool-context</code> is now disabled when instantiating
+  <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wint-in-bool-context"><code>-Wint-in-bool-context</code></a>
+    is now disabled when instantiating
       a template (<a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=3a2b12bc">git</a>)</li>
   <li>Stricter checking of attributes on friend declarations: if a friend
       declaration has an attribute, that declaration must be a definition.
@@ -304,13 +310,15 @@ a work-in-progress.</p>
       and <code>-Wc++23-extensions</code>.  They are enabled by default
       and can be used to control existing pedwarns about occurences of
       new C++ constructs in code using an old C++ standard dialect.</li>
-  <li>New warning <code>-Wmissing-requires</code> warns about missing
-      <code>requires</code>
+  <li>New warning
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wmissing-requires"><code>-Wmissing-requires</code></a>
+      warns about missing <code>requires</code>
       (<a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=e18e56c7">git</a>)</li>
   <li>The existing <code>std::is_constant_evaluated</code> in <code>if</code>
       warning was extended to warn in more cases
       (<a href="https://gcc.gnu.org/PR100995">PR100995</a>)</li>
-  <li><code>-Waddress</code> has been enhanced so that it now warns about, for
+  <li><a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Waddress"><code>-Waddress</code></a>
+      has been enhanced so that it now warns about, for
       instance, comparing the address of a nonstatic member function to null
       (<a href="https://gcc.gnu.org/PR102103">PR102103</a>)</li>
   <li>Errors about narrowing are no longer hidden if they occur in system
@@ -332,7 +340,9 @@ a work-in-progress.</p>
   <li><code>constinit thread_local</code> variables are optimized better
       (<a href="https://gcc.gnu.org/PR101786">PR101786</a>)</li>
   <li>Support for C++17 <code>std::hardware_destructive_interference_size</code>
-      was added, along with the <code>-Winterference-size</code> warning
+      was added, along with the
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Winterference-size"><code>-Winterference-size</code></a>
+      warning
       (<a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=76b75018">git</a>)</li>
   <li>Many bugs in the CTAD handling have been fixed
       (<a href="https://gcc.gnu.org/PR101344">PR101344</a>,
@@ -643,16 +653,19 @@ a work-in-progress.</p>
 <h3 id="uninitialized">Eliminating uninitialized variables</h3>
 
 <ul>
-  <li>GCC can now initialize all stack variables implicitly, including
+  <li>GCC can now <a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-ftrivial-auto-var-init">initialize all stack variables implicitly</a>, including
       padding. This is intended to eliminate all classes of uninitialized
       stack variable flaws. Lack of explicit initialization will still
-      warn when <code>-Wuninitialized</code> is active. For best
-      debugging, use of the new command-line option
-      <code>-ftrivial-auto-var-init=pattern</code> can be used to fill
-      variables with a repeated <code>0xFE</code> pattern, which tends to
+      warn when
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wuninitialized"><code>-Wuninitialized</code></a>
+      is active. For best debugging, use of the new command-line option
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-ftrivial-auto-var-init"><code>-ftrivial-auto-var-init=pattern</code></a>
+      can be used to fill variables with a repeated <code>0xFE</code> pattern, which tends to
       illuminate many bugs (e.g. pointers receive invalid addresses, sizes
       and indices are very large). For best production results, the new
-      command-line option <code>-ftrivial-auto-var-init=zero</code> can be
+      command-line option
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-ftrivial-auto-var-init"><code>-ftrivial-auto-var-init=zero</code></a>
+      can be
       used to fill variables with <code>0x00</code>, which tends to provide
       a safer state for bugs (e.g. pointers are <code>NULL</code>, strings
       are <code>NUL</code> filled, and sizes and indices are <code>0</code>).

commit f370b62b8dae4d0ec11a957f5c3817039aca3958
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Wed Mar 30 10:07:48 2022 -0400

    gcc-12: jit changes

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index f82f1a97..ed555e31 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -405,7 +405,40 @@ a work-in-progress.</p>
 <!-- <h3 id="go">Go</h3> -->
 
 <!-- .................................................................. -->
-<!-- <h2 id="jit">libgccjit</h2> -->
+<h2 id="jit">libgccjit</h2>
+
+<ul>
+  <li>The libgccjit API gained 23 new entry points:
+    <ul>
+      <li>17 new "reflection" entrypoints for querying functions and types (<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-16"><code>LIBGCCJIT_ABI_16</code></a>)
+      </li>
+      <li>
+	<a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_lvalue_set_tls_model"><code>gcc_jit_lvalue_set_tls_model</code></a>
+	for supporting thread-local variables
+	(<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-17"><code>LIBGCCJIT_ABI_17</code></a>)
+      </li>
+      <li>
+	<a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_lvalue_set_link_section"><code>gcc_jit_lvalue_set_link_section</code></a>
+	for setting the link section of global variables, analogous to
+	<a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#index-section-variable-attribute"><code>__attribute__((section(".section")))</code></a>
+	(<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-18"><code>LIBGCCJIT_ABI_18</code></a>)
+      </li>
+      <li>4 new entrypoints for initializing global variables and creating
+	constructors for rvalues
+	(<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-19"><code>LIBGCCJIT_ABI_19</code></a>)
+      </li>
+    </ul>
+  </li>
+  <li>libgccjit has gained support for the use of various atomic builtins
+    (<a href="https://gcc.gnu.org/PR96066">PR96066</a>,
+    <a href="https://gcc.gnu.org/PR96067">PR96067</a>)
+  </li>
+  <li><a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_context_new_cast">gcc_jit_context_new_cast</a>
+    is now able to handle truncation and extension between different
+    integer types
+    (<a href="https://gcc.gnu.org/PR95498">PR95498</a>)
+  </li>
+</ul>
 
 <!-- .................................................................. -->
 <h2 id="targets">New Targets and Target Specific Improvements</h2>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-12/changes.html | 82 ++++++++++++++++++++++++++++++++++++----------
 1 file changed, 64 insertions(+), 18 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2022-04-01 14:29 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=20220401142958.029053858D28@sourceware.org \
    --to=dmalcolm@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: 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).