summaryrefslogtreecommitdiffstats
path: root/clang/docs/DriverInternals.rst
diff options
context:
space:
mode:
authorJustin Bogner <mail@justinbogner.com>2015-07-03 08:03:43 +0000
committerJustin Bogner <mail@justinbogner.com>2015-07-03 08:03:43 +0000
commit2d74ae53f27229c45493f2a7f98d35135b6ccc7f (patch)
treee1d84e82d6c44acb3b5a43d548ae613873c33168 /clang/docs/DriverInternals.rst
parent6a8e75c7351fb3bcbb9cd36640b299f370d2ad1e (diff)
downloadbcm5719-llvm-2d74ae53f27229c45493f2a7f98d35135b6ccc7f.tar.gz
bcm5719-llvm-2d74ae53f27229c45493f2a7f98d35135b6ccc7f.zip
Driver: Replace a couple of out of date terms in the docs
The Job base class was removed in r241310, so replace a couple of references to it with Command. Also change another use of Job with Action, since that's the term used in the source. llvm-svn: 241327
Diffstat (limited to 'clang/docs/DriverInternals.rst')
-rw-r--r--clang/docs/DriverInternals.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/clang/docs/DriverInternals.rst b/clang/docs/DriverInternals.rst
index 4cd2e5dfe6b..6bc5f7dac95 100644
--- a/clang/docs/DriverInternals.rst
+++ b/clang/docs/DriverInternals.rst
@@ -155,7 +155,7 @@ The driver functionality is conceptually divided into five stages:
Subsequent stages should rarely, if ever, need to do any string
processing.
-#. **Pipeline: Compilation Job Construction**
+#. **Pipeline: Compilation Action Construction**
Once the arguments are parsed, the tree of subprocess jobs needed for
the desired compilation sequence are constructed. This involves
@@ -266,7 +266,7 @@ The driver functionality is conceptually divided into five stages:
#. **Translate: Tool Specific Argument Translation**
Once a Tool has been selected to perform a particular Action, the
- Tool must construct concrete Jobs which will be executed during
+ Tool must construct concrete Commands which will be executed during
compilation. The main work is in translating from the gcc style
command line options to whatever options the subprocess expects.
@@ -280,7 +280,7 @@ The driver functionality is conceptually divided into five stages:
last of arguments corresponding to some option, or all arguments for
an option.
- The result of this stage is a list of Jobs (executable paths and
+ The result of this stage is a list of Commands (executable paths and
argument strings) to execute.
#. **Execute**
OpenPOWER on IntegriCloud