gccint: Including Patterns

1 
1 17.17 Including Patterns in Machine Descriptions.
1 =================================================
1 
1 The 'include' pattern tells the compiler tools where to look for
1 patterns that are in files other than in the file '.md'.  This is used
1 only at build time and there is no preprocessing allowed.
1 
1  It looks like:
1 
1 
1      (include
1        PATHNAME)
1 
1  For example:
1 
1 
1      (include "filestuff")
1 
1 
1  Where PATHNAME is a string that specifies the location of the file,
1 specifies the include file to be in 'gcc/config/target/filestuff'.  The
1 directory 'gcc/config/target' is regarded as the default directory.
1 
1  Machine descriptions may be split up into smaller more manageable
1 subsections and placed into subdirectories.
1 
1  By specifying:
1 
1 
1      (include "BOGUS/filestuff")
1 
1 
1  the include file is specified to be in
1 'gcc/config/TARGET/BOGUS/filestuff'.
1 
1  Specifying an absolute path for the include file such as;
1 
1      (include "/u2/BOGUS/filestuff")
1 
1  is permitted but is not encouraged.
1 
1 17.17.1 RTL Generation Tool Options for Directory Search
1 --------------------------------------------------------
1 
1 The '-IDIR' option specifies directories to search for machine
1 descriptions.  For example:
1 
1 
1      genrecog -I/p1/abc/proc1 -I/p2/abcd/pro2 target.md
1 
1 
1  Add the directory DIR to the head of the list of directories to be
1 searched for header files.  This can be used to override a system
1 machine definition file, substituting your own version, since these
1 directories are searched before the default machine description file
1 directories.  If you use more than one '-I' option, the directories are
1 scanned in left-to-right order; the standard default directory come
1 after.
1