public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paulo Matos <pmatos@linki.tools>
To: David Malcolm <dmalcolm@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update)
Date: Mon, 29 Jan 2018 14:27:00 -0000	[thread overview]
Message-ID: <dc65d8a5-5320-0a63-3f8e-e7981027bb4e@linki.tools> (raw)
In-Reply-To: <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

  reply	other threads:[~2018-01-29 14:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  8:56 GCC Buildbot Update Paulo Matos
2017-12-14 11:39 ` David Malcolm
2017-12-15  9:16   ` Paulo Matos
2017-12-15 14:29     ` David Malcolm
2017-12-16 11:07       ` Paulo Matos
2018-01-24 19:20         ` jamais-vu can now ignore renumbering of source lines in dg output (Re: GCC Buildbot Update) David Malcolm
2018-01-25  7:25           ` Paulo Matos
2018-01-29 13:55           ` Paulo Matos
2018-01-29 14:19             ` David Malcolm
2018-01-29 14:27               ` Paulo Matos [this message]
2017-12-14 20:32 ` GCC Buildbot Update Christophe Lyon
2017-12-15  7:42   ` Markus Trippelsdorf
2017-12-15  9:21     ` Paulo Matos
2017-12-15 11:10       ` Markus Trippelsdorf
2017-12-15 17:05     ` Segher Boessenkool
2017-12-16 11:54       ` Paulo Matos
2017-12-15  9:19   ` Paulo Matos
2017-12-15  9:21     ` Christophe Lyon
2017-12-15  9:29       ` Paulo Matos
2017-12-20  8:32       ` Paulo Matos
2017-12-20  9:52         ` Christophe Lyon
2017-12-20 10:02           ` Paulo Matos
2017-12-20 10:09             ` Christophe Lyon
2017-12-20 11:49             ` James Greenhalgh
2017-12-20 14:01               ` Paulo Matos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dc65d8a5-5320-0a63-3f8e-e7981027bb4e@linki.tools \
    --to=pmatos@linki.tools \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).