From: "Martin Liška" <mliska@suse.cz>
To: David Malcolm <dmalcolm@redhat.com>, GCC Development <gcc@gcc.gnu.org>
Cc: Jan Hubicka <hubicka@ucw.cz>,
Richard Biener <richard.guenther@gmail.com>,
Michael Matz <matz@suse.de>, Martin Jambor <mjambor@suse.cz>
Subject: Re: How big (and fast) is going to be GCC 8?
Date: Tue, 06 Mar 2018 16:18:00 -0000 [thread overview]
Message-ID: <e8660eb2-d0ec-fad1-9863-fe439f39bdd9@suse.cz> (raw)
In-Reply-To: <1520349196.2913.66.camel@redhat.com>
On 03/06/2018 04:13 PM, David Malcolm wrote:
> On Tue, 2018-03-06 at 11:14 +0100, Martin Liška wrote:
>> Hello.
>>
>> Many significant changes has landed in mainline and will be released
>> as GCC 8.1.
>> I decided to use various GCC configs we have and test how there
>> configuration differ
>> in size and also binary size.
>>
>> This is first part where I measured binary size, speed comparison
>> will follow.
>> Configuration names should be self-explaining, the 'system-*' is
>> built done
>> without bootstrap with my system compiler (GCC 7.3.0). All builds are
>> done
>> on my Intel Haswell machine.
>>
>> Feel free to reply if you need any explanation.
>> Martin
>
> Some possibly silly questions:
Hi David.
All of them are qualified!
>
> (a) was this done with:
> --enable-checking=release ?
Yes.
>
> (b) is this measuring cc1 ?
cc1plus. Let me also add cc1 when I'll have run-time numbers.
>
> (c) are the units bytes? (so ~183MB for the unstripped system-O2-
> native cc1, ~25MB after stripping?)
Yes, in bytes. Would be nicer to have it in MB ;) It would be easily
readable. I'll fix that.
>
> (d) do you have comparable data for gcc 7?
Will build corresponding builds for GCC 7 tonight.
Martin
>
> Thanks
> Dave
>
next prev parent reply other threads:[~2018-03-06 16:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 10:14 Martin Liška
2018-03-06 15:13 ` David Malcolm
2018-03-06 16:18 ` Martin Liška [this message]
2018-03-06 18:35 ` Martin Liška
2018-03-06 17:50 ` How big (and fast) is going to be GCC 8? [part 2] Martin Liška
2018-03-06 18:16 ` Bin.Cheng
2018-03-06 18:36 ` Martin Liška
2018-03-07 9:26 ` Size and speed comparison of GCC 7 & 8 Martin Liška
2018-03-07 10:13 ` Martin Liška
2018-03-07 11:12 ` Martin Liška
2018-03-13 13:31 ` Martin Liška
2018-03-20 19:57 ` How can compiler speed-up postgresql database? Martin Liška
2018-03-21 9:26 ` Richard Biener
2018-03-21 9:34 ` Martin Liška
2018-03-21 11:47 ` Jan Hubicka
2019-04-15 11:44 ` GCC 8 vs. GCC 9 speed and size comparison Martin Liška
2019-04-15 12:12 ` Michael Matz
2019-04-15 13:20 ` Jan Hubicka
2019-04-15 13:33 ` Jakub Jelinek
2019-04-15 15:08 ` Michael Matz
2019-04-16 7:48 ` Martin Liška
2019-04-16 8:17 ` Martin Liška
2019-04-16 8:53 ` Michael Matz
2019-04-16 9:56 ` Richard Biener
2019-04-16 11:25 ` Richard Biener
2019-04-16 11:39 ` Jakub Jelinek
2019-04-16 11:54 ` Richard Biener
[not found] <5ec1f1c1-e0f6-5681-b6c6-cf8b076bc02a@suse.cz>
2018-03-06 10:32 ` How big (and fast) is going to be GCC 8? Richard Biener
2018-03-06 14:59 ` Jan Hubicka
2018-03-12 15:05 ` Jan Hubicka
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=e8660eb2-d0ec-fad1-9863-fe439f39bdd9@suse.cz \
--to=mliska@suse.cz \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=matz@suse.de \
--cc=mjambor@suse.cz \
--cc=richard.guenther@gmail.com \
/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).