diff options
Diffstat (limited to 'gcc/doc/sourcebuild.texi')
| -rw-r--r-- | gcc/doc/sourcebuild.texi | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index 5026de7..4e913fe 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -192,8 +192,8 @@ files, kept in the top level directory, are used. FIXME: when is the the top level one) used? @item The file @file{config.gcc} is used to handle configuration -specific to the particular target machine. The file -@file{config.build} is used to handle configuration specific to the +specific to the particular target machine. The file +@file{config.build} is used to handle configuration specific to the particular build machine. The file @file{config.host} is used to handle configuration specific to the particular host machine. (In general, these should only be used for features that cannot reasonably be tested in @@ -276,7 +276,7 @@ headers to work with GCC, some other headers may also be installed in @file{config} to be installed on some systems. GCC installs its own version of @code{<float.h>}, from @file{ginclude/float.h}. -This is done to cope with command-line options that change the +This is done to cope with command-line options that change the representation of floating point numbers. GCC also installs its own version of @code{<limits.h>}; this is generated @@ -901,13 +901,13 @@ GCC contains the following C language test suites, in the @table @file @item gcc.dg -This contains tests of particular features of the C compiler, using the +This contains tests of particular features of the C compiler, using the more modern @samp{dg} harness. Correctness tests for various compiler features should go here if possible. -Magic comments determine whether the file -is preprocessed, compiled, linked or run. In these tests, error and warning -message texts are compared against expected texts or regular expressions +Magic comments determine whether the file +is preprocessed, compiled, linked or run. In these tests, error and warning +message texts are compared against expected texts or regular expressions given in comments. These tests are run with the options @samp{-ansi -pedantic} unless other options are given in the test. Except as noted below they are not run with multiple optimization options. @@ -936,7 +936,7 @@ FIXME: describe this. This contains particular code fragments which have historically broken easily. These tests are run with multiple optimization options, so tests for features which only break at some optimization levels belong here. This also contains -tests to check that certain optimizations occur. It might be worthwhile to +tests to check that certain optimizations occur. It might be worthwhile to separate the correctness tests cleanly from the code quality tests, but it hasn't been done yet. |