public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61578] [4.9 regression] Code size increase for ARM thumb compared to 4.8.x when compiling with -Os Date: Thu, 03 Sep 2015 14:59:00 -0000 [thread overview] Message-ID: <bug-61578-4-E5Tt41Uyou@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61578-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61578 --- Comment #24 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- (In reply to Fredrik Hederstierna from comment #23) > Thanks for your patch, I tried it out, and it solves the small example fine, > the code now is similar to GCC 4.8 for this particular example. > > Though when I ran the full CSiBE benchmark, the code size unfortunately grew > approx +150 bytes overall for the full suite. So the patch did not solve the > generic root problem with code size increase unfortunately. > > This is strange and I'm thinking of how to continue from here, this issue > has diverged a bit too much (mostly because of my own fault) with several > examples etc. Do you think we should create separate issues for different > small examples that compiles bad perhaps? but on the same time we need to > keep track on the 'generic' overall code size issue as eg. CSiBE points out. > Either way will work for me. The most important is to have test cases somewhere in Bigzilla on which I could work. I did not expect that the patch solves CSiBE code size degradation. Therefore I wrote "a patch for" instead of "patch solving the problem". I expect it will be a long work to solve the problem. > Here's is another small example I tested yesterday that also gives > unnecessary moves, both for arm7tdmi, arm966e-s and cortex-m0 tested. > Thanks. I'll will investigate it.
next prev parent reply other threads:[~2015-09-03 14:59 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-21 10:32 [Bug c/61578] New: " fredrik.hederstierna@securitas-direct.com 2014-06-21 10:33 ` [Bug c/61578] " fredrik.hederstierna@securitas-direct.com 2014-06-21 10:34 ` fredrik.hederstierna@securitas-direct.com 2014-06-21 10:34 ` fredrik.hederstierna@securitas-direct.com 2014-06-21 10:35 ` fredrik.hederstierna@securitas-direct.com 2014-06-21 10:35 ` fredrik.hederstierna@securitas-direct.com 2014-07-24 14:42 ` [Bug target/61578] " ramana at gcc dot gnu.org 2014-08-14 14:23 ` vmakarov at gcc dot gnu.org 2014-09-23 21:45 ` fredrik.hederstierna@securitas-direct.com 2014-11-02 20:35 ` fredrik.hederstierna@securitas-direct.com 2014-11-02 20:38 ` fredrik.hederstierna@securitas-direct.com 2014-11-03 1:33 ` zhenqiang.chen at arm dot com 2014-12-12 15:03 ` ramana at gcc dot gnu.org 2015-01-15 11:25 ` [Bug target/61578] [4.9/ 5 regression] " ramana at gcc dot gnu.org 2015-02-09 0:11 ` [Bug target/61578] [4.9/5 " pinskia at gcc dot gnu.org 2015-03-02 10:02 ` fredrik.hederstierna@securitas-direct.com 2015-03-03 16:05 ` law at redhat dot com 2015-06-26 19:57 ` [Bug target/61578] [4.9 " jakub at gcc dot gnu.org 2015-06-26 20:29 ` jakub at gcc dot gnu.org 2015-08-18 14:29 ` fredrik.hederstierna@securitas-direct.com 2015-08-18 14:41 ` fredrik.hederstierna@securitas-direct.com 2015-08-19 10:56 ` fredrik.hederstierna@securitas-direct.com 2015-09-01 14:06 ` vmakarov at gcc dot gnu.org 2015-09-01 14:16 ` fredrik.hederstierna@securitas-direct.com 2015-09-01 19:38 ` vmakarov at gcc dot gnu.org 2015-09-03 5:16 ` fredrik.hederstierna@securitas-direct.com 2015-09-03 14:59 ` vmakarov at gcc dot gnu.org [this message] 2015-09-08 21:38 ` fredrik.hederstierna@securitas-direct.com 2015-09-10 20:18 ` vmakarov at gcc dot gnu.org 2015-09-22 17:13 ` vogt at linux dot vnet.ibm.com 2015-09-22 17:41 ` vogt at linux dot vnet.ibm.com 2015-09-23 12:16 ` vogt at linux dot vnet.ibm.com 2015-09-24 20:38 ` vmakarov at gcc dot gnu.org 2015-09-24 20:41 ` vmakarov at gcc dot gnu.org 2015-09-25 9:12 ` vogt at linux dot vnet.ibm.com 2015-09-28 9:12 ` vogt at linux dot vnet.ibm.com
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-61578-4-E5Tt41Uyou@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).