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. c7b2066195cbfd33927c7b8fa571bf844fad9826 Date: Mon, 18 May 2020 16:18:38 +0000 (GMT) [thread overview] Message-ID: <20200518161838.910123851C13@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2228 bytes --] 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 c7b2066195cbfd33927c7b8fa571bf844fad9826 (commit) from 72fc30f8b51df7340d2df3399fbfe34f57784652 (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 c7b2066195cbfd33927c7b8fa571bf844fad9826 Author: David Malcolm <dmalcolm@redhat.com> Date: Mon May 18 11:58:33 2020 -0400 wwwdocs: add GCC 10 jit changes 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> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-18 16:18 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=20200518161838.910123851C13@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: linkBe 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).