I've gone ahead and pushed this patch to the website.
No new validation errors.
---
htdocs/gcc-10/changes.html | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 2bc25d92..abbafa58 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -632,7 +632,21 @@ int get_naïve_pi() {
<!-- <h3 id="go">Go</h3> -->
<!-- .................................................................. -->
-<!-- <h2 id="jit">libgccjit</h2> -->
+<h2 id="jit">libgccjit</h2>
+<ul>
+ <li>
+ The libgccjit API gained four new entry points:
+ <ul>
+ <li>
+ <a
href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#c.gcc_jit_version_major";>gcc_jit_version_major</a>,
+ <a
href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#c.gcc_jit_version_minor";>gcc_jit_version_minor</a>,
and
+ <a
href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#c.gcc_jit_version_patchlevel";>gcc_jit_version_patchlevel</a>
+ for programmatically checking the libgccjit version from client code,
and
+ </li>
+ <li><a
href="https://gcc.gnu.org/onlinedocs/jit/topics/types.html#c.gcc_jit_context_new_bitfield";>gcc_jit_context_new_bitfield</a></li>
+ </ul>
+ </li>
+</ul>
<!-- .................................................................. -->
<h2 id="targets">New Targets and Target Specific Improvements</h2>
--
2.21.0
