Built on x86_64-pc-linux-gnu, does this look OK for trunk and perhaps
release branches?
-- >8 --
Jonathan noticed this flag isn't documented in the manual.
gcc/ChangeLog:
* doc/invoke.texi: Add -fconcepts-diagnostics-depth.
---
gcc/doc/invoke.texi | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index d7f51b4f6d93..a7feeabd795e 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -213,7 +213,8 @@ in the following sections.
@gccoptlist{-fabi-version=@var{n} -fno-access-control
-faligned-new=@var{n} -fno-assume-sane-operators-new-delete
-fchar8_t -fcheck-new
--fconcepts -fconstexpr-depth=@var{n} -fconstexpr-cache-depth=@var{n}
+-fconcepts -fconcepts-diagnostic-depth=@var{n}
+-fconstexpr-depth=@var{n} -fconstexpr-cache-depth=@var{n}
-fconstexpr-loop-limit=@var{n} -fconstexpr-ops-limit=@var{n}
-fno-elide-constructors
-fno-enforce-eh-specs
@@ -3160,6 +3161,11 @@ into the standard, could additionally be enabled by
in GCC 14 and removed in GCC 15; users are expected to convert their code
to C++20 concepts.
+@opindex fconcepts-diagnostics-depth
+@item -fconcepts-diagnostics-depth=@var{n}
+Set the maximum nested elaboration depth for concepts satisfaction failure
+diagnostics. The default is 1.
+
@opindex fconstexpr-depth
@item -fconstexpr-depth=@var{n}
Set the maximum nested evaluation depth for C++11 constexpr functions
--
2.50.0.rc1
