This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH/Merge Request] Vtable Verification feature.

On Tue, Aug 6, 2013 at 11:43 AM, Caroline Tice <> wrote:
> On Tue, Aug 6, 2013 at 11:31 AM, Ian Lance Taylor <> wrote:
>>The output to the file doesn't have
>> any indication of what file is being compiled, so it will be ambiguous
>> when run in parallel.
> You are mistaken.  It outputs one line to the log file for each compilation
> unit.  The output line begins with the name of the file that was being
> compiled.  In my use case, I have used this to build a very large system,
> which resulted in something like at 8000 line log file of counts, which I
> then used my sum script on to see how the verifications were going.

I was mistaken in detail but I'm not sure I was mistaken in principle.
What happens if you are building the large system twice in different
directories on the same machine?  Or, for that matter, if two
different people are doing so?  Or if one person did it a while ago,
and now you want to do it, but you can't open the file because it is
owned by the other person?

Maybe you should simply change -fvtv-counts to take a file name, then
we don't have to worry about any of this.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]