Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-05 Thread Nathan Sidwell
On 06/05/2017 12:31 PM, Bernd Edlinger wrote: So how about this new patch? Is it OK for trunk? Yes thanks. nathan -- Nathan Sidwell

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-05 Thread Bernd Edlinger
On 06/05/17 13:11, Nathan Sidwell wrote: > +Compile the source files additionally with @option{-fprofile-abs-path} > +to create absolute path names in the @file{.gcno} files. This allows > +@command{gcov} to find the correct sources in projects with multiple > +directories. > > I think the second

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-05 Thread Nathan Sidwell
On 06/02/2017 10:43 AM, Bernd Edlinger wrote: On 06/02/17 13:35, Nathan Sidwell wrote: On 06/01/2017 03:24 PM, Bernd Edlinger wrote: This is a gcc option that converts relative path names to absolute ones, so that gcov can properly merge the line numbers in projects where different relative pa

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-02 Thread Bernd Edlinger
On 06/02/17 13:35, Nathan Sidwell wrote: > On 06/01/2017 03:24 PM, Bernd Edlinger wrote: > >> This is a gcc option that converts relative >> path names to absolute ones, so that gcov can >> properly merge the line numbers in projects >> where different relative path names may refer >> to the same

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-02 Thread Nathan Sidwell
On 06/01/2017 03:24 PM, Bernd Edlinger wrote: This is a gcc option that converts relative path names to absolute ones, so that gcov can properly merge the line numbers in projects where different relative path names may refer to the same source file. Thanks. From reading the patch though, I d

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-01 Thread Bernd Edlinger
On 06/01/17 19:52, Nathan Sidwell wrote: > On 06/01/2017 11:59 AM, Bernd Edlinger wrote: >> Ping... > > What are you asking to be reviewed by who? > > nathan > Aehm, sorry. This is a gcc option that converts relative path names to absolute ones, so that gcov can properly merge the line numbers

Re: [PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-01 Thread Nathan Sidwell
On 06/01/2017 11:59 AM, Bernd Edlinger wrote: Ping... What are you asking to be reviewed by who? nathan -- Nathan Sidwell

[PING**3] [PATCH] Force use of absolute path names for gcov

2017-06-01 Thread Bernd Edlinger
Ping... On 05/12/17 18:47, Bernd Edlinger wrote: > Ping... > > On 04/28/17 19:41, Bernd Edlinger wrote: >> Ping... >> >> I attached a rebased patch file, with the doc changes and >> merge conflicts with trunk of today fixed, but otherwise >> identical. >> >> >> Thanks >> Bernd. >> >> On 04/21/17

[PING**2] [PATCH] Force use of absolute path names for gcov

2017-05-12 Thread Bernd Edlinger
Ping... On 04/28/17 19:41, Bernd Edlinger wrote: > Ping... > > I attached a rebased patch file, with the doc changes and > merge conflicts with trunk of today fixed, but otherwise > identical. > > > Thanks > Bernd. > > On 04/21/17 22:26, Bernd Edlinger wrote: >> >> >> On 04/21/17 21:50, Joseph Mye

[PING] [PATCH] Force use of absolute path names for gcov

2017-04-28 Thread Bernd Edlinger
Ping... I attached a rebased patch file, with the doc changes and merge conflicts with trunk of today fixed, but otherwise identical. Thanks Bernd. On 04/21/17 22:26, Bernd Edlinger wrote: > > > On 04/21/17 21:50, Joseph Myers wrote: >> On Fri, 21 Apr 2017, Bernd Edlinger wrote: >> >>> So I wou

Re: [PATCH] Force use of absolute path names for gcov

2017-04-21 Thread Bernd Edlinger
On 04/21/17 21:50, Joseph Myers wrote: > On Fri, 21 Apr 2017, Bernd Edlinger wrote: > >> So I would like to add a -fprofile-abs-path option that >> forces absolute path names in gcno files, which allows gcov >> to get the true canonicalized source name. > > I don't see any actual documentation of

Re: [PATCH] Force use of absolute path names for gcov

2017-04-21 Thread Joseph Myers
On Fri, 21 Apr 2017, Bernd Edlinger wrote: > So I would like to add a -fprofile-abs-path option that > forces absolute path names in gcno files, which allows gcov > to get the true canonicalized source name. I don't see any actual documentation of this option in the patch (you add it to the summ

[PATCH] Force use of absolute path names for gcov

2017-04-21 Thread Bernd Edlinger
Hi! If gcov is used in projects where gcc is invoked in different directories, it may happen that the same source is compiled with different relative names, and the gcov tool is thus unable to find out, if it is the same source file or not, or to dump the source at all, which is a limitation of t