OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix DOS-based system build and fix documentation.

Browse Source 
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
This commit is contained in:
Martin Liska 2018-07-04 09:32:16 +02:00 committed by Martin Liska
parent f45eb40805
commit 7709f595ef
3 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gcc/ChangeLog
View File

@ -1,3 +1,9 @@
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

2
gcc/coverage.c
View File

@ -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

7
gcc/doc/invoke.texi
View File

@ -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