PR tree-optimization/19853
[official-gcc.git] / gcc / ada / gnatcmd.ads
blobe7b9578f19a8bb4e6e0290a304c833f791a9e081
1 ------------------------------------------------------------------------------
2 -- --
3 -- GNAT COMPILER COMPONENTS --
4 -- --
5 -- G N A T C M D --
6 -- --
7 -- S p e c --
8 -- --
9 -- Copyright (C) 1996 Free Software Foundation, Inc. --
10 -- --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 2, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --
17 -- for more details. You should have received a copy of the GNU General --
18 -- Public License distributed with GNAT; see file COPYING. If not, write --
19 -- to the Free Software Foundation, 59 Temple Place - Suite 330, Boston, --
20 -- MA 02111-1307, USA. --
21 -- --
22 -- GNAT was originally developed by the GNAT team at New York University. --
23 -- Extensive contributions were provided by Ada Core Technologies Inc. --
24 -- --
25 ------------------------------------------------------------------------------
27 -- This program provides a simple command interface for using GNAT and its
28 -- associated utilities. The format of switches accepted is intended to
29 -- be more familiar in style for VMS and DOS users than the standard Unix
30 -- style switches that are accepted directly.
32 -- The program is typically called GNAT when it is installed and
33 -- the two possibile styles of use are:
35 -- To call gcc:
37 -- GNAT filename switches
39 -- To call the tool gnatxxx
41 -- GNAT xxx filename switches
43 -- where xxx is the command name (e.g. MAKE for gnatmake). This command name
44 -- can be abbreviated by giving a prefix (e.g. GNAT MAK) as long as it
45 -- remains unique.
47 -- In both cases, filename is in the format appropriate to the operating
48 -- system in use. The individual commands give more details. In some cases
49 -- a unit name may be given in place of a file name.
51 -- The switches start with a slash. Switch names can also be abbreviated
52 -- where no ambiguity arises. The switches associated with each command
53 -- are specified by the tables that can be found in the body.
55 -- Although by convention we use upper case for command names and switches
56 -- in the documentation, all command and switch names are case insensitive
57 -- and may be given in upper case or lower case or a mixture.
59 procedure GNATCmd;