From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH 5/9] wwwdocs: gcc-14: libgccjit changes
Date: Thu, 4 Apr 2024 12:42:04 -0400 [thread overview]
Message-ID: <20240404164208.2437213-6-dmalcolm@redhat.com> (raw)
In-Reply-To: <20240404164208.2437213-1-dmalcolm@redhat.com>
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
---
htdocs/gcc-14/changes.html | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 95ed00c9..2dc7e598 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -360,7 +360,36 @@ 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 6 new entry points:
+ <ul>
+ <li>
+ <!-- commit r14-3552-g29763b002459cb -->
+ <a href="https://gcc.gnu.org/onlinedocs/jit/topics/types.html#c.gcc_jit_type_get_restrict"><code>gcc_jit_type_get_restrict</code></a>
+ for adding <code>restrict</code> to types
+ (<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-25"><code>LIBGCCJIT_ABI_25</code></a>).
+ </li>
+ <li>
+ <!-- commit r14-7177-g109985343bcada -->
+ 4 functions for setting attributes on functions and variables
+ (<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-26"><code>LIBGCCJIT_ABI_26</code></a>):
+ <ul>
+ <li>gcc_jit_function_add_attribute</li>
+ <li>gcc_jit_function_add_string_attribute</li>
+ <li>gcc_jit_function_add_integer_array_attribute</li>
+ <li>gcc_jit_lvalue_add_string_attribute</li>
+ </ul>
+ </li>
+ <li>
+ <!-- commit r14-8760-g5d534a214bf966 -->
+ <a href="https://gcc.gnu.org/onlinedocs/jit/topics/expressions.html#c.gcc_jit_context_new_sizeof"><code>gcc_jit_context_new_sizeof</code></a>
+ for accessing the size of a type
+ (<a href="https://gcc.gnu.org/onlinedocs/jit/topics/compatibility.html#libgccjit-abi-27"><code>LIBGCCJIT_ABI_27</code></a>).
+ </li>
+ </ul>
+ </li>
+</ul>
<!-- .................................................................. -->
<h2 id="targets">New Targets and Target Specific Improvements</h2>
--
2.39.2
next prev parent reply other threads:[~2024-04-04 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 16:41 [pushed] wwwdocs: gcc-14: various changes David Malcolm
2024-04-04 16:42 ` [PATCH 1/9] wwwdocs: gcc-14: add caveat about not using analyzer on C++ David Malcolm
2024-04-04 16:42 ` [PATCH 2/9] wwwdocs: gcc-14: add URLs to some options David Malcolm
2024-04-07 19:32 ` Hans-Peter Nilsson
2024-04-04 16:42 ` [PATCH 3/9] wwwdocs: gcc-14: add null_terminated_string_arg attribute David Malcolm
2024-04-04 16:42 ` [PATCH 4/9] wwwdocs: gcc-14: c++: note changes to source quoting in template errors David Malcolm
2024-04-04 16:42 ` David Malcolm [this message]
2024-04-04 16:42 ` [PATCH 6/9] wwwdocs: gcc-14: improvements to automatic doc URLs for options David Malcolm
2024-04-04 16:42 ` [PATCH 7/9] wwwdocs: gcc-14: improvements for plugin authors David Malcolm
2024-04-04 16:42 ` [PATCH 8/9] wwwdocs: gcc-14: analyzer improvements David Malcolm
2024-04-04 16:42 ` [PATCH 9/9] wwwdocs: gcc-14: add 'Improvements to SARIF support' section David Malcolm
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=20240404164208.2437213-6-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@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).