ada: Update gnat-llvm debugging documentation for nested functions

We recently changed gdb so that it can directly handle gnat-style
unnesting.  This fixes an issue with debugging nested functions with
gnat-llvm.

gcc/ada/ChangeLog:

	* doc/gnat_ugn/building_executable_programs_with_gnat.rst
	(GNATLLVM): Remove note about nested functions.
	* gnat_ugn.texi: Regenerate.

diff --git a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
index c69b958804cf642c8c802984a2412e54681715fe..a67047107b24049a394b4e887d0e425a413fa0b7 100644 (file)
--- a/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
+++ b/gcc/ada/doc/gnat_ugn/building_executable_programs_with_gnat.rst
@@ -8005,11 +8005,8 @@ GNAT LLVM currently provides limited support for debugging data. It
 provides full line number information for declarations and statements,
 and complete debugging data for all types.
 
-In some situations, a name in the source may not be available.
-Renamings are not currently emitted into the debugging data. When
-debugging a nested function, variables from enclosing scopes will not
-be available. You will have to examine those variables in their
-hosting frame.
+In some situations, a name in the source may not be available.  For
+example, renamings are not currently emitted into the debugging data.
 
 In addition, debugging information may be confusing if you have
 ``out`` parameters to subprograms. If you have a procedure with only

diff --git a/gcc/ada/gnat_ugn.texi b/gcc/ada/gnat_ugn.texi
index 6350a4a99ef9d77c6e6b2b018b5b3877da32246c..f1d887c3670c0a2465a1861e93c6295786ebea58 100644 (file)
--- a/gcc/ada/gnat_ugn.texi
+++ b/gcc/ada/gnat_ugn.texi
@@ -17571,11 +17571,8 @@ GNAT LLVM currently provides limited support for debugging data. It
 provides full line number information for declarations and statements,
 and complete debugging data for all types.
 
-In some situations, a name in the source may not be available.
-Renamings are not currently emitted into the debugging data. When
-debugging a nested function, variables from enclosing scopes will not
-be available. You will have to examine those variables in their
-hosting frame.
+In some situations, a name in the source may not be available.  For
+example, renamings are not currently emitted into the debugging data.
 
 In addition, debugging information may be confusing if you have
 @code{out} parameters to subprograms. If you have a procedure with only
@@ -30270,8 +30267,8 @@ to permit their use in free software.
 
 @printindex ge
 
-@anchor{gnat_ugn/gnat_utility_programs switches-related-to-project-files}@w{                              }
 @anchor{d2}@w{                              }
+@anchor{gnat_ugn/gnat_utility_programs switches-related-to-project-files}@w{                              }
 
 @c %**end of body
 @bye