> From: Martin Liška
> Sent: Thursday, June 20, 2019 9:49 AM
> I see. What about the following patch:
>
> $ ./gcc/xgcc -Bgcc /tmp/main.c --coverage -fprofile-note=/tmp/main.gcno $
> ls -l /tmp/main.gcno
> -rw-r--r-- 1 marxin users 428 Jun 20 15:48 /tmp/main.gcno
Thanks. That did the trick.
Nex
Dell Customer Communication - Confidential
> From: Martin Liška
> Sent: Thursday, June 20, 2019 9:49 AM
> I see. What about the following patch:
>
> $ ./gcc/xgcc -Bgcc /tmp/main.c --coverage
> -fprofile-note=/tmp/main.gcno $ ls -l /tmp/main.gcno
> -rw-r--r-- 1 marxin users 428 Jun 20 15:48 /tm
On 6/20/19 3:29 PM, david.tay...@dell.com wrote:
>> From: Martin Liška
>> Sent: Thursday, June 20, 2019 9:07 AM
>>
>> On 6/20/19 3:00 PM, david.tay...@dell.com wrote:
>>>
From: Martin Liška
Sent: Thursday, June 20, 2019 5:12 AM
On 6/19/19 7:11 PM, david.tay...@dell.com wrote:
> From: Martin Liška
> Sent: Thursday, June 20, 2019 9:07 AM
>
> On 6/20/19 3:00 PM, david.tay...@dell.com wrote:
> >
> >> From: Martin Liška
> >> Sent: Thursday, June 20, 2019 5:12 AM
> >>
> >> On 6/19/19 7:11 PM, david.tay...@dell.com wrote:
> >>> Thanks for the patch. Standalone it is not su
> Am 20.06.19 um 15:00 schrieb david.tay...@dell.com:
> > Dell Customer Communication - Confidential
>
> Can't expect me to read this, then? :-)
Grumble. For every email, even internal ones, we are asked
it's 'sensitivity'. I explicitly marked that one as 'external public'.
It should not have s
On 6/20/19 3:00 PM, david.tay...@dell.com wrote:
> Dell Customer Communication - Confidential
>
>> From: Martin Liška
>> Sent: Thursday, June 20, 2019 5:12 AM
>> To: taylor, david; richard.guent...@gmail.com
>> Cc: gcc@gcc.gnu.org
>> Subject: Re: gcc: -ftest
Am 20.06.19 um 15:00 schrieb david.tay...@dell.com:
Dell Customer Communication - Confidential
Can't expect me to read this, then? :-)
Dell Customer Communication - Confidential
> From: Martin Liška
> Sent: Thursday, June 20, 2019 5:12 AM
> To: taylor, david; richard.guent...@gmail.com
> Cc: gcc@gcc.gnu.org
> Subject: Re: gcc: -ftest-coverage and -auxbase
>
> On 6/19/19 7:11 PM, david.tay...@dell.com wrot
On 6/19/19 7:11 PM, david.tay...@dell.com wrote:
> Thanks for the patch. Standalone it is not sufficient. Combined
> with the other two changes that have been discussed --
Why is that not sufficient? If you build from top-level and you have .o files
that overwrite each other, then you can set
-
Dell Customer Communication - Confidential
> From: Martin Liška
> Sent: Wednesday, June 19, 2019 3:19 AM
>
> On 6/18/19 11:51 PM, david.tay...@dell.com wrote:
> >> From: Martin Liška
> >> Sent: Tuesday, June 18, 2019 11:20 AM
> >>
> >> .gcno files are created during compilation and contain info
On 6/18/19 11:51 PM, david.tay...@dell.com wrote:
>> From: Martin Liška
>> Sent: Tuesday, June 18, 2019 11:20 AM
>>
>> .gcno files are created during compilation and contain info about a source
>> file.
>> These files will be created by a cross compiler, so that's fine.
>>
>> During a run of a pr
> From: Martin Liška
> Sent: Tuesday, June 18, 2019 11:20 AM
>
> .gcno files are created during compilation and contain info about a source
> file.
> These files will be created by a cross compiler, so that's fine.
>
> During a run of a program a .gcda file is created. It contains information
On 6/18/19 3:31 PM, david.tay...@dell.com wrote:
> Dell Customer Communication - Confidential
>
>> From: Martin Liška
>> Sent: Tuesday, June 18, 2019 4:56 AM
>>
>> On 6/18/19 10:40 AM, Richard Biener wrote:
>>> I don't think we want to expose -auxbase. Iff then an alternate way
>>> to specify a
Dell Customer Communication - Confidential
> From: Martin Liška
> Sent: Tuesday, June 18, 2019 4:56 AM
>
> On 6/18/19 10:40 AM, Richard Biener wrote:
> > I don't think we want to expose -auxbase. Iff then an alternate way
> > to specify a coverage output file name.
>
> I'm not aware of it.
>
On 6/18/19 10:40 AM, Richard Biener wrote:
> I don't think we want to expose -auxbase. Iff then an alternate way to
> specify
> a coverage output file name.
I'm not aware of it.
@David: Can you please summarize what you want to achieve with the .gcno files?
I can then help you.
Martin
On Mon, Jun 17, 2019 at 5:02 PM wrote:
>
> > From: Richard Biener
> > Sent: Monday, June 17, 2019 9:57 AM
> > To: taylor, david
> > Cc: GCC Development
> > Subject: Re: gcc: -ftest-coverage and -auxbase
>
> > On Mon, Jun 17, 2019 at 2:46 PM David Tayl
> From: Richard Biener
> Sent: Monday, June 17, 2019 9:57 AM
> To: taylor, david
> Cc: GCC Development
> Subject: Re: gcc: -ftest-coverage and -auxbase
> On Mon, Jun 17, 2019 at 2:46 PM David Taylor wrote:
> >
> > From: Richard Biener
> > D
On Mon, Jun 17, 2019 at 2:46 PM David Taylor wrote:
>
> Sorry for the late reply. Your message never arrived in my mailbox.
> I suspect that corporate email has swallowed it for some stupid
> reason. I'm replying to a copy I found in the mailing list archives
> at gcc dot gnu dot org. Hopefully
Sorry for the late reply. Your message never arrived in my mailbox.
I suspect that corporate email has swallowed it for some stupid
reason. I'm replying to a copy I found in the mailing list archives
at gcc dot gnu dot org. Hopefully I didn't screw up the editing.
From: Richard Biener
On Wed, Jun 12, 2019 at 10:17 PM wrote:
>
> When doing a build, we use a pipe between GCC and GAS.
> And because we wish to do some analysis of the assembly code,
> we do not use -pipe but instead do '-S -c -'. And this has worked
> fine for many years.
Can you please show us complete command-li
When doing a build, we use a pipe between GCC and GAS.
And because we wish to do some analysis of the assembly code,
we do not use -pipe but instead do '-S -c -'. And this has worked
fine for many years.
I was recently looking into collecting some coverage information.
To that end, I added --cove
21 matches
Mail list logo
