Clearly document behaviour of multiple -g options

This copies the wording from the -O options to clearly state what
happens if more than one -g option is used.

	* doc/invoke.texi (Debugging Options): Explicitly state the semantics
	of using multiple -g options.

From-SVN: r270257

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 522538c5d54551bd8294d78c290c060372c39bcc..6249828a73abdc1539ba36755747355ef9713a84 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2019-04-10  Jonathan Wakely  <jwakely@redhat.com>
+
+       * doc/invoke.texi (Debugging Options): Explicitly state the semantics
+       of using multiple -g options.
+
 2019-04-10  Martin Liska  <mliska@suse.cz>
 
        PR gcov-profile/89959

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index cfc3063929b09e46d34ac425c72da78b808d1e8e..73a7789d879b8a73e66659c4698e485b2dd796fd 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -7818,6 +7818,9 @@ Level 3 includes extra information, such as all the macro definitions
 present in the program.  Some debuggers support macro expansion when
 you use @option{-g3}.
 
+If you use multiple @option{-g} options, with or without level numbers,
+the last such option is the one that is effective.
+
 @option{-gdwarf} does not accept a concatenated debug level, to avoid
 confusion with @option{-gdwarf-@var{level}}.
 Instead use an additional @option{-g@var{level}} option to change the