From: "Martin Liška" <mliska@suse.cz>
To: "Bin.Cheng" <amker.cheng@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>, 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? [part 2]
Date: Tue, 06 Mar 2018 18:36:00 -0000 [thread overview]
Message-ID: <310f39c3-ee1f-88c8-92e5-16fcfdd7d27e@suse.cz> (raw)
In-Reply-To: <CAHFci2-_UsMOosMHTWzvjn1Gnb+7fvKMD3ahbrEwqjHRHDWW_w@mail.gmail.com>
On 03/06/2018 07:16 PM, Bin.Cheng wrote:
> On Tue, Mar 6, 2018 at 5:50 PM, Martin Liška <mliska@suse.cz> wrote:
>> Hi.
>>
>> This is speed comparison of GCC 8 builds compared to my system GCC 7.3.0
>> which is built with PGO bootstrap.
>>
>> I run empty C and C++ source file, tramp3d and the rest are some big beasts
>> from GCC source file. Feel free to suggest another test candidates? Note
>> that first column defines how many times was test run.
> First thanks very much for collecting the data.
> Since we enabled several loop passes at O3 and above levels, some data
> for Ofast might be interesting?
Do you have a nice source file full of loop nests that would test that
properly?
Martin
>
> Thanks,
> bin
>>
>> Martin
next prev parent reply other threads:[~2018-03-06 18:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 10:14 How big (and fast) is going to be GCC 8? Martin Liška
2018-03-06 15:13 ` David Malcolm
2018-03-06 16:18 ` Martin Liška
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 [this message]
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
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=310f39c3-ee1f-88c8-92e5-16fcfdd7d27e@suse.cz \
--to=mliska@suse.cz \
--cc=amker.cheng@gmail.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).