public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [PATCH 7/9] wwwdocs: gcc-14: improvements for plugin authors
Date: Thu,  4 Apr 2024 12:42:06 -0400	[thread overview]
Message-ID: <20240404164208.2437213-8-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 | 23 ++++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 0701dc29..8b72bc20 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -761,7 +761,28 @@ __asm (".global __flmap_lock"  "\n\t"
 </ul>
 
 <!-- .................................................................. -->
-<!-- <h2 id="plugins">Improvements for plugin authors</h2> -->
+<h2 id="plugins">Improvements for plugin authors</h2>
+<ul>
+  <li>
+    <!-- commmit r14-4006-g3a1e9f3ed7aa49 -->
+    GCC diagnostics have been able to have execution paths associated
+    with them since GCC 10, but previously these were required to be
+    single-threaded.
+    As of GCC 14, these execution paths can have multipled named threads
+    associated with them, with each event being associated with one of the
+    threads.
+    No existing GCC diagnostics take advantage of this, but GCC plugins
+    may find this useful for their own diagnostics; an
+    <a href="https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=3a1e9f3ed7aa49adad02190ace0614e0b37fc089">example</a>
+    is provided in the testsuite.
+  </li>
+  <li>
+    <!-- commit r14-6057-g12b67d1e13b3cf -->
+    GCC's diagnostics can now optionally add per-diagnostic property
+    bags to the SARIF output, allowing plugins to capture custom data
+    as needed with their diagnostics.
+  </li>
+</ul>
 
 <!-- .................................................................. -->
 <h2>Other significant improvements</h2>
-- 
2.39.2


  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 ` [PATCH 5/9] wwwdocs: gcc-14: libgccjit changes David Malcolm
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 ` David Malcolm [this message]
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-8-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).