On Tue, Apr 30, 2024 at 10:24:44 +0100, Jonathan Wakely wrote:
> On 20/11/23 11:22 -0500, Ben Boeckel wrote:
> >---
> > 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
> 
> This should be -fdeps-target= not -fdeps=target=.

Whoops, yep.

> >+      (the <code>p1689r5</code> format is the only available format today).
> 
> I wish the option was more descriptive than "p1689r5", which nobody is
> going to remember (but I assume we don't actually need to specify it
> explicitly since it's the only supported format).

All users of the flag should be having it in the build system itself;
hand-coded makefiles can use it, but will need considerable `jq`
gymnastics to turn the output into properly understood make syntax
snippets for their build.

> >+      </li>
> >+    </ul>
> 
> Do we need a list for this item? It seems a bit weird that the first
> list item is just the paper  How about just a single paragraph?
> 
> C++ module scanning for named modules is now available, based on the
> format described in <a href="https://wg21.link/P1689R5";>P1689R5</a>,
> Format for describing dependencies of source files. The
> <code>-fdeps-format=</code>, <code>-fdeps-file=</code>, and
> <code>-fdeps-target=</code> flags may be used to generate dependency
> information. In GCC 14 <code>p1689r5</code> is the only valid argument
> for <code>-fdeps-format=</code>.

Sounds good. New patch attached.

--Ben
>From d973efa9689db7d46211721e7c00feea7e6445a6 Mon Sep 17 00:00:00 2001
From: Ben Boeckel <ben.boec...@kitware.com>
Date: Thu, 2 May 2024 14:00:01 -0400
Subject: [PATCH 1/1] gcc-14: document P1689R5 scanning output support

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 8dfbf7dc..8998e6c0 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -513,6 +513,12 @@ a work-in-progress.</p>
   <li>GCC supports a new pragma <code>&#x23;pragma GCC novector</code> to
       indicate to the vectorizer not to vectorize the loop annotated with the
       pragma.</li>
+  <li>C++ module scanning for named modules is now available, based on the
+    format described in<a href="https://wg21.link/P1689R5";>P1689R5</a>, Format 
for
+    describing dependencies of source files. The <code>-fdeps-format=</code>,
+    <code>-fdeps-file=</code>, and <code>-fdeps-target=</code> flags may be
+    used to generate dependency information. In GCC 14 <code>p1689r5</code> is
+    the only valid argument for <code>-fdeps-format=</code>.</li>
 </ul>
 
 <h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
-- 
2.44.0

Reply via email to