This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update)
- From: Paulo Matos <pmatos@linki.tools>
- To: David Malcolm <dmalcolm at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 29 Jan 2018 15:27:23 +0100
- Subject: Re: jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update)
- Authentication-results: sourceware.org; auth=none
- References: <f664b74e-8751-24ed-139f-443ce3f1cdef@linki.tools> <1513251583.27881.199.camel@redhat.com> <b38f19dc-7dc9-af7a-4f00-593605e00d42@linki.tools> <1513348171.27881.230.camel@redhat.com> <306f5617-e62a-b828-c075-ba821cd2e361@linki.tools> <1516821601.26503.8.camel@redhat.com> <5a698304-34bc-019c-7197-6386a5320bbb@linki.tools> <1517235585.26503.38.camel@redhat.com>
On 29/01/18 15:19, David Malcolm wrote:
>>
>> Hi,
>>
>> I am looking at this today and I noticed that having the source file
>> for
>> all recent GCC revisions is costly in terms of time (if we wish to
>> compress them) and space (for storage). I was instead thinking that
>> jv
>> could calculate the differences offline using pysvn and the old and
>> new
>> revision numbers.
>
> Note that access to the source files is optional - jv doesn't need
> them, it just helps for the particular situation described above.
>
I understand but it would be great to have line number filtering.
>> I have started implementing this in my port. Would you consider
>> merging it?
>
> Sounds reasonable - though bear in mind that gcc might be switching to
> git at some point.
>
Yes, I know... but... if we wait for that to happen to implement
something... :)
> Send a pull request (I've turned on travis CI on the github repository,
> so pull requests now automatically get tested on a bunch of different
> Python 3 versions).
>
Sure.
--
Paulo Matos