public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65478] [5 regression] crafty performance regression Date: Wed, 01 Apr 2015 17:51:00 -0000 [thread overview] Message-ID: <bug-65478-4-PYnQ6pEj9G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65478-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65478 --- Comment #23 from Jan Hubicka <hubicka at ucw dot cz> --- > Seems to be a regression with -flto only? I also see EON regressing without > -flto. Yes, the inlining is cross file. > > http://gcc.opensuse.org/SPEC/CINT/sb-megrez-head-64/index.html Saw that one too. It is in between Feb 10, 2015 18:20 UTC (Values: Base: 164.gzip: 1558, 175.vpr: 2392, 176.gcc: 2845, 181.mcf: 3766, 186.crafty: 2926, 197.parser: 1975, 252.eon: 3726, 255.vortex: 3305, 256.bzip2: 2218, 300.twolf: 3257 Peak: , 164.gzip: 1546, 175.vpr: 2397, 176.gcc: 1994, 181.mcf: 3819, 186.crafty: 2737, 197.parser: 1911, 252.eon: 4461, 255.vortex: 4364, 256.bzip2: 2348, 300.twolf: 3265) Feb 10, 2015 09:20 UTC (Values: Base: 164.gzip: 1549, 175.vpr: 2452, 176.gcc: 2734, 181.mcf: 3458, 186.crafty: 2833, 197.parser: 1962, 252.eon: 4083, 255.vortex: 3378, 256.bzip2: 2059, 300.twolf: 3231 Peak: , 164.gzip: 1555, 175.vpr: 2241, 176.gcc: 2800, 181.mcf: 3821, 186.crafty: 2681, 197.parser: 1905, 252.eon: 4415, 255.vortex: 4363, 256.bzip2: 2379, 300.twolf: 3220) So it does not seem to point to inliner changes (fortunately). At Megrez, you should be able to access the diff? Honza
next prev parent reply other threads:[~2015-04-01 17:51 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-19 22:38 [Bug tree-optimization/65478] New: " hubicka at gcc dot gnu.org 2015-03-19 22:45 ` [Bug tree-optimization/65478] " hubicka at gcc dot gnu.org 2015-03-20 2:51 ` [Bug ipa/65478] [5 regression] " hubicka at gcc dot gnu.org 2015-03-20 10:24 ` rguenth at gcc dot gnu.org 2015-03-20 18:25 ` hubicka at ucw dot cz 2015-03-20 19:19 ` hubicka at ucw dot cz 2015-03-24 14:10 ` jamborm at gcc dot gnu.org 2015-03-24 17:23 ` hubicka at ucw dot cz 2015-03-24 18:48 ` jamborm at gcc dot gnu.org 2015-03-25 7:57 ` hubicka at ucw dot cz 2015-03-27 9:45 ` jamborm at gcc dot gnu.org 2015-03-27 9:49 ` jamborm at gcc dot gnu.org 2015-03-29 14:15 ` hubicka at gcc dot gnu.org 2015-03-29 17:46 ` hubicka at gcc dot gnu.org 2015-03-30 2:23 ` hubicka at gcc dot gnu.org 2015-03-30 11:27 ` rguenth at gcc dot gnu.org 2015-03-30 17:53 ` hubicka at ucw dot cz 2015-03-30 20:02 ` glisse at gcc dot gnu.org 2015-03-30 21:40 ` hubicka at gcc dot gnu.org 2015-03-31 12:14 ` rguenther at suse dot de 2015-03-31 13:08 ` rguenth at gcc dot gnu.org 2015-04-01 14:43 ` rguenth at gcc dot gnu.org 2015-04-01 17:51 ` hubicka at ucw dot cz [this message] 2015-04-02 8:38 ` rguenther at suse dot de 2015-04-05 23:55 ` hubicka at gcc dot gnu.org 2015-04-07 8:49 ` rguenth at gcc dot gnu.org
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=bug-65478-4-PYnQ6pEj9G@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).