[commit] Use @value{NGCC} for the proper name of GCC

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[commit] Use @value{NGCC} for the proper name of GCC

Eli Zaretskii
I noticed that most of our uses of @value{GCC} are incorrect, and
fixed that as shown below.

Committed.

2007-01-26  Eli Zaretskii  <[hidden email]>

        * gdb.texinfo (Compilation, Files, Bootstrapping, Bug Reporting):
        Use @value{NGCC} instead of @value{GCC}.

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.379
diff -u -r1.379 gdb.texinfo
--- gdb/doc/gdb.texinfo 20 Jan 2007 16:51:55 -0000 1.379
+++ gdb/doc/gdb.texinfo 26 Jan 2007 08:52:41 -0000
@@ -4491,7 +4491,7 @@
 @c underflow problems.
 @cindex frameless execution
 Some compilers provide a way to compile functions so that they operate
-without stack frames.  (For example, the @value{GCC} option
+without stack frames.  (For example, the @value{NGCC} option
 @smallexample
 @samp{-fomit-frame-pointer}
 @end smallexample
@@ -11499,7 +11499,7 @@
 generated for that environment; you may use either a @sc{gnu} compiler, or
 other compilers that adhere to the local conventions.
 Best results are usually obtained from @sc{gnu} compilers; for example,
-using @code{@value{GCC}} you can generate debugging information for
+using @code{@value{NGCC}} you can generate debugging information for
 optimized code.
 
 For most kinds of object files, with the exception of old SVR3 systems
@@ -13176,7 +13176,7 @@
 If you do not use the GNU C compiler, you may need other standard
 library subroutines as well; this varies from one stub to another,
 but in general the stubs are likely to use any of the common library
-subroutines which @code{@value{GCC}} generates as inline code.
+subroutines which @code{@value{NGCC}} generates as inline code.
 
 
 @node Debug Session
@@ -21930,7 +21930,7 @@
 @item
 What compiler (and its version) was used to compile the program you are
 debugging---e.g.@:  ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP
-C Compiler''.  For GCC, you can say @code{gcc --version} to get this
+C Compiler''.  For @value{NGCC}, you can say @kbd{gcc --version} to get this
 information; for other compilers, see the documentation for those
 compilers.