* [PATCH 1/1] gcc-14: document P1689R5 scanning output support
@ 2023-11-20 13:26 Ben Boeckel
0 siblings, 0 replies; 4+ messages in thread
From: Ben Boeckel @ 2023-11-20 13:26 UTC (permalink / raw)
To: gcc-patches; +Cc: brad.king, Ben Boeckel
---
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH 1/1] gcc-14: document P1689R5 scanning output support
@ 2023-11-20 16:22 Ben Boeckel
2024-01-03 15:34 ` Ben Boeckel
2024-04-30 9:24 ` Jonathan Wakely
0 siblings, 2 replies; 4+ messages in thread
From: Ben Boeckel @ 2023-11-20 16:22 UTC (permalink / raw)
To: gcc-patches; +Cc: brad.king, Ben Boeckel
---
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 1/1] gcc-14: document P1689R5 scanning output support
2023-11-20 16:22 Ben Boeckel
@ 2024-01-03 15:34 ` Ben Boeckel
2024-04-30 9:24 ` Jonathan Wakely
1 sibling, 0 replies; 4+ messages in thread
From: Ben Boeckel @ 2024-01-03 15:34 UTC (permalink / raw)
To: gcc-patches; +Cc: brad.king
On Mon, Nov 20, 2023 at 11:22:56 -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
> + (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
Ping? Is this the right place to submit this patch?
Thanks,
--Ben
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 1/1] gcc-14: document P1689R5 scanning output support
2023-11-20 16:22 Ben Boeckel
2024-01-03 15:34 ` Ben Boeckel
@ 2024-04-30 9:24 ` Jonathan Wakely
1 sibling, 0 replies; 4+ messages in thread
From: Jonathan Wakely @ 2024-04-30 9:24 UTC (permalink / raw)
To: Ben Boeckel; +Cc: gcc-patches, brad.king
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=.
>+ (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).
>+ </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>.
>+ </li>
> </ul>
>
> <h4 id="libstdcxx">Runtime Library (libstdc++)</h4>
>--
>2.42.0
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-04-30 9:24 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-20 13:26 [PATCH 1/1] gcc-14: document P1689R5 scanning output support Ben Boeckel
2023-11-20 16:22 Ben Boeckel
2024-01-03 15:34 ` Ben Boeckel
2024-04-30 9:24 ` Jonathan Wakely
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).