public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65478] [5 regression] crafty performance regression Date: Mon, 30 Mar 2015 02:23:00 -0000 [thread overview] Message-ID: <bug-65478-4-5f9BGbNkLX@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 #15 from Jan Hubicka <hubicka at gcc dot gnu.org> --- The inline bump needed is about 23. Richard, i guess convincing early optimizers to turn that hack into shifts (that is done by GCC but only at RTL time), is out of reach for this release, right?
next prev parent reply other threads:[~2015-03-29 22:10 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 [this message] 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 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-5f9BGbNkLX@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).