Hi.
I'm sending fix for DOS-based system, it's a compilation error that
I introduced some time ago. Plus I add Jonathan's correction of a documentation
entry.
Ready for trunk?
Thanks,
Martin
gcc/ChangeLog:
2018-07-03 Martin Liska <mli...@suse.cz>
Jonathan Wakely <jwak...@redhat.com>
* coverage.c: Use correct type.
* doc/invoke.texi: Language correction.
---
gcc/coverage.c | 2 +-
gcc/doc/invoke.texi | 7 ++++---
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/gcc/coverage.c b/gcc/coverage.c
index 9c9d3dbd39e..da171c84d3c 100644
--- a/gcc/coverage.c
+++ b/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
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 56cd122b0d7..31d4f1047ba 100644
--- a/gcc/doc/invoke.texi
+++ b/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
