From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [pushed] wwwdocs: gcc-14: various changes
Date: Thu, 4 Apr 2024 12:41:59 -0400 [thread overview]
Message-ID: <20240404164208.2437213-1-dmalcolm@redhat.com> (raw)
I've taken the liberty of pushing the following changes
to the GCC 14 release notes. Hope they look reasonable.
David Malcolm (9):
gcc-14: add caveat about not using analyzer on C++
gcc-14: add URLs to some options
gcc-14: add null_terminated_string_arg attribute
gcc-14: c++: note changes to source quoting in template errors
gcc-14: libgccjit changes
gcc-14: improvements to automatic doc URLs for options
gcc-14: improvements for plugin authors
gcc-14: analyzer improvements
gcc-14: add 'Improvements to SARIF support' section
htdocs/gcc-14/changes.html | 294 +++++++++++++++++++++++++++++++++++--
1 file changed, 284 insertions(+), 10 deletions(-)
--
2.39.2
next 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 David Malcolm [this message]
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 ` [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-1-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).