Fix DOS-based system build and fix documentation.

2018-07-04  Martin Liska  <mliska@suse.cz>
            Jonathan Wakely  <jwakely@redhat.com>

	* coverage.c: Use correct type.
	* doc/invoke.texi: Language correction.

Co-Authored-By: Jonathan Wakely <jwakely@redhat.com>

From-SVN: r262373

gcc/ChangeLog

+2018-07-04  Martin Liska  <mliska@suse.cz>
+            Jonathan Wakely  <jwakely@redhat.com>
+
+	* coverage.c: Use correct type.
+	* doc/invoke.texi: Language correction.
+
 2018-07-03  H.J. Lu  <hongjiu.lu@intel.com>
 
 	PR target/85620

gcc/coverage.c

@@ -1227,7 +1227,7 @@ coverage_init (const char *filename)
       if (profile_data_prefix)
 	{
 #if HAVE_DOS_BASED_FILE_SYSTEM
-	  const char separator = "\\";
+	  const char *separator = "\\";
 #else
 	  const char *separator = "/";
 #endif

gcc/doc/invoke.texi

@@ -11352,9 +11352,10 @@ and used by @option{-fprofile-use} and @option{-fbranch-probabilities}
 and its related options.  Both absolute and relative paths can be used.
 By default, GCC uses the current directory as @var{path}, thus the
 profile data file appears in the same directory as the object file.
-In order to prevent filename clashing, if object file name is not an absolute
-path, we mangle absolute path of @file{@var{sourcename}.gcda} file and
-use it as file name of a @file{.gcda} file.
+In order to prevent the file name clashing, if the object file name is
+not an absolute path, we mangle the absolute path of the
+@file{@var{sourcename}.gcda} file and use it as the file name of a
+@file{.gcda} file.
 
 When an executable is run in a massive parallel environment, it is recommended
 to save profile to different folders.  That can be done with variables