public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ben Boeckel <ben.boeckel@kitware.com>
To: gcc-patches@gcc.gnu.org
Cc: brad.king@kitware.com, Ben Boeckel <ben.boeckel@kitware.com>
Subject: [PATCH 1/1] gcc-14: document P1689R5 scanning output support
Date: Mon, 20 Nov 2023 11:22:56 -0500	[thread overview]
Message-ID: <20231120162256.3620350-1-ben.boeckel@kitware.com> (raw)

---
 htdocs/gcc-14/changes.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 7278f753..b506eeb1 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -112,6 +112,17 @@ a work-in-progress.</p>
       </li>
     </ul>
   </li>
+  <li>C++ module scanning for named modules is now available:
+    <ul>
+      <li><a href="https://wg21.link/P1689R5">P1689R5</a>, Format for
+      describing dependencies of source files.
+      </li>
+      <li>The <code>-fdeps-format=</code>, <code>-fdeps-file=</code>, and
+      <code>-fdeps=target=</code> flags may be used to generate P1689 output
+      (the <code>p1689r5</code> format is the only available format today).
+      </li>
+    </ul>
+  </li>
 </ul>
 
 <h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
-- 
2.42.0


             reply	other threads:[~2023-11-20 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20 16:22 Ben Boeckel [this message]
2024-01-03 15:34 ` Ben Boeckel
2024-01-06 13:17   ` [PATCH wwwdocs " Arsen Arsenović
2024-04-27 23:39     ` Ben Boeckel
2024-04-30  9:24 ` [PATCH " Jonathan Wakely
2024-05-02 18:03   ` [PATCHv2 wwwdocs " Ben Boeckel
2024-05-07 10:05     ` Jonathan Wakely
  -- strict thread matches above, loose matches on Subject: below --
2023-11-20 13:26 [PATCH " Ben Boeckel

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=20231120162256.3620350-1-ben.boeckel@kitware.com \
    --to=ben.boeckel@kitware.com \
    --cc=brad.king@kitware.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).