From: "Martin Liška" <mliska@suse.cz>
To: GCC Development <gcc@gcc.gnu.org>
Subject: C-Vise: speed?
Date: Wed, 13 May 2020 16:41:21 +0200 [thread overview]
Message-ID: <997cd74a-5fe6-6cb5-6773-130a348e458e@suse.cz> (raw)
In-Reply-To: <6b46bf76-4779-9555-de46-ee4fae8e2a3b@suse.cz>
Hello.
I've made some measurements for GCC PRs that I've reduced recently:
- PR92516 - C++ - 6.5MB
C-Reduce: 77 minutes
C-Vise: 35 minutes
- PR94523 - C++ - 2.1MB
C-Reduce: 33 minutes
C-Vise: 15 minutes
- PR94632 - C++ - 3.3MB
C-Reduce: 28 minutes
C-Vise: 20 minutes
- PR94937 - C++ - 8.5MB
C-Reduce: 303 minutes
C-Vise: 242 minutes
Note that I also added cvise-delta, which simulates popular delta tool,
but runs in a parallel mode.
Martin
prev parent reply other threads:[~2020-05-13 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 12:50 C-Vise project introduction Martin Liška
2020-05-13 14:41 ` Martin Liška [this message]
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=997cd74a-5fe6-6cb5-6773-130a348e458e@suse.cz \
--to=mliska@suse.cz \
--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).