From: Sandra Loosemore <sandra@codesourcery.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [doc, 1/n] invoke.texi: name of gcc executable
Date: Tue, 12 Jan 2016 17:45:00 -0000 [thread overview]
Message-ID: <56953BA4.8090004@codesourcery.com> (raw)
In-Reply-To: <5692EE28.1070502@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
I've checked in the first installment of my planned reorganization of
the invoke.texi chapter. Here I've deleted the section placed randomly
in the middle of option descriptions that contained only a paragraph
about the name of the gcc executable, and incorporated that information
into the chapter introduction instead. I did a little bit of editing of
the text in the introduction as well, and rewrote the one reference to
the deleted node so it makes sense without it.
-Sandra
[-- Attachment #2: gccdoc.log --]
[-- Type: text/x-log, Size: 298 bytes --]
2016-01-12 Sandra Loosemore <sandra@codesourcery.com>
gcc/
* doc/invoke.texi (Invoking GCC): Copy-edit. Incorporate information
about name of GCC executable. Remove deleted node from menu.
(Directory Options) <-B>: Remove cross-reference to deleted node.
(Target Options): Delete section.
[-- Attachment #3: gccdoc.patch --]
[-- Type: text/x-patch, Size: 3698 bytes --]
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 232279)
+++ gcc/doc/invoke.texi (working copy)
@@ -72,8 +72,9 @@ assembly and linking. The ``overall opt
process at an intermediate stage. For example, the @option{-c} option
says not to run the linker. Then the output consists of object files
output by the assembler.
+@xref{Overall Options,,Options Controlling the Kind of Output}.
-Other options are passed on to one stage of processing. Some options
+Other options are passed on to one or more stages of processing. Some options
control the preprocessor and others the compiler itself. Yet other
options control the assembler and linker; most of these are not
documented here, since you rarely need to use any of them.
@@ -85,9 +86,18 @@ for C programs; when an option is only u
for a particular option does not mention a source language, you can use
that option with all supported languages.
-@cindex C++ compilation options
-@xref{Invoking G++,,Compiling C++ Programs}, for a summary of special
-options for compiling C++ programs.
+@cindex cross compiling
+@cindex specifying machine version
+@cindex specifying compiler version and target machine
+@cindex compiler version, specifying
+@cindex target machine, specifying
+The usual way to run GCC is to run the executable called @command{gcc}, or
+@command{@var{machine}-gcc} when cross-compiling, or
+@command{@var{machine}-gcc-@var{version}} to run a specific version of GCC.
+When you compile C++ programs, you should invoke GCC as @command{g++}
+instead. @xref{Invoking G++,,Compiling C++ Programs},
+for information about the differences in behavior between @command{gcc}
+and @code{g++} when compiling C++ programs.
@cindex grouping options
@cindex options, grouping
@@ -137,7 +147,6 @@ only one of these two forms, whichever o
* Directory Options:: Where to find header files and libraries.
Where to find the compiler executable files.
* Spec Files:: How to pass switches to sub-processes.
-* Target Options:: Running a cross-compiler, or an old version of GCC.
* Submodel Options:: Specifying minor hardware or convention variations,
such as 68010 vs 68020.
* Code Gen Options:: Specifying conventions for function calls, data layout
@@ -11733,7 +11742,8 @@ include files, and data files of the com
The compiler driver program runs one or more of the subprograms
@command{cpp}, @command{cc1}, @command{as} and @command{ld}. It tries
@var{prefix} as a prefix for each program it tries to run, both with and
-without @samp{@var{machine}/@var{version}/} (@pxref{Target Options}).
+without @samp{@var{machine}/@var{version}/} for the corresponding target
+machine and compiler version.
For each subprogram to be run, the compiler driver first tries the
@option{-B} prefix, if any. If that name is not found, or if @option{-B}
@@ -12409,20 +12419,6 @@ proper position among the other output f
@c man begin OPTIONS
-@node Target Options
-@section Specifying Target Machine and Compiler Version
-@cindex target options
-@cindex cross compiling
-@cindex specifying machine version
-@cindex specifying compiler version and target machine
-@cindex compiler version, specifying
-@cindex target machine, specifying
-
-The usual way to run GCC is to run the executable called @command{gcc}, or
-@command{@var{machine}-gcc} when cross-compiling, or
-@command{@var{machine}-gcc-@var{version}} to run a version other than the
-one that was installed last.
-
@node Submodel Options
@section Hardware Models and Configurations
@cindex submodel options
next prev parent reply other threads:[~2016-01-12 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 23:50 [doc, 0/n] improve organization of invoke.texi Sandra Loosemore
2016-01-12 17:45 ` Sandra Loosemore [this message]
2016-01-13 0:48 ` [doc, 1.5/n] invoke.texi: reclassify -no-canonical-prefixes and -specs= Sandra Loosemore
2016-01-13 3:31 ` [doc, 2/n] invoke.texi: move spec file section Sandra Loosemore
2016-01-13 21:08 ` [doc, 3/n] invoke.texi: move "Code Gen Options" before target-specific options Sandra Loosemore
2016-01-25 0:16 ` Gerald Pfeifer
2016-01-13 23:38 ` [doc, 3.5/n] invoke.texi: rename "Machine-Dependent Options" section Sandra Loosemore
2016-01-15 2:00 ` [doc, 4/n] invoke.texi: there is no part 4 Sandra Loosemore
2016-01-15 2:18 ` [doc, 5/n] invoke.texi: add new "Program Instrumentation Options" section Sandra Loosemore
2016-01-15 8:39 ` Mikhail Maltsev
2016-01-15 15:52 ` Sandra Loosemore
2016-01-17 4:12 ` [doc, 6/n] invoke.texi: split debugging options into programmer vs developer sections Sandra Loosemore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56953BA4.8090004@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).