public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jingyu at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/39871] [4.3/4.4/4.5 regression] Code size increase on ARM due to inferior CSE
Date: Wed, 10 Feb 2010 12:18:00 -0000 [thread overview]
Message-ID: <20100210121840.26227.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39871-17592@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from jingyu at google dot com 2010-02-10 12:18 -------
I still get the 10-instruction code with trunk GCC I checked out today.
$arm-eabi-gcc -mthumb -mthumb-interwork -fpic -Os code.c -S
test:
push {lr}
sub sp, sp, #20
ldr r2, [r0]
add r3, sp, #4
ldr r1, [r0, #4]
str r2, [r3, #4]
mov r0, r3
bl func
add sp, sp, #20
@ sp needed for prologue
pop {r0}
bx r0
.size test, .-test
.ident "GCC: (GNU) 4.5.0 20100210 (experimental)"
The toolchain was built with newlib-1.17.0, mpc-0.8.1, mpfr-2.4.1, gmp-4.2.4,
binutils-2.19.
Target: arm-eabi
Configured with:
/usr/local/home/projects/newlib_armtoolchain/gcc-trunk-read/configure
--prefix=/usr/local/home/projects/toolchain_build/newlib_build_trunk/install
--target=arm-eabi --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--with-gmp=/usr/local/home/projects/toolchain_build/newlib_build_trunk/install
--with-mpfr=/usr/local/home/projects/toolchain_build/newlib_build_trunk/install
--with-mpc=/usr/local/home/projects/toolchain_build/newlib_build_trunk/install
--enable-multilib --with-newlib --with-gnu-as --with-gnu-ld
--enable-languages=c,c++
Thread model: single
gcc version 4.5.0 20100210 (experimental) (GCC)
Steven, could you please share how you build the toolchain which generates the
9-instruction code?
Thanks!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39871
next prev parent reply other threads:[~2010-02-10 12:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 16:16 [Bug rtl-optimization/39871] New: [4.3/4.4/4.5 regression] CSE doesn't work alexvod at google dot com
2009-04-24 9:14 ` [Bug rtl-optimization/39871] " rguenth at gcc dot gnu dot org
2009-05-05 15:41 ` [Bug rtl-optimization/39871] [4.3/4.4/4.5 regression] Code size increase on ARM due to inferior CSE mmitchel at gcc dot gnu dot org
2009-05-06 15:07 ` bonzini at gnu dot org
2009-05-20 14:17 ` ramana at gcc dot gnu dot org
2009-06-14 10:24 ` mikpe at it dot uu dot se
2009-06-14 14:06 ` mikpe at it dot uu dot se
2009-08-04 12:49 ` rguenth at gcc dot gnu dot org
2010-01-02 0:21 ` steven at gcc dot gnu dot org
2010-01-02 10:29 ` bonzini at gnu dot org
2010-01-02 10:31 ` bonzini at gnu dot org
2010-02-08 11:15 ` steven at gcc dot gnu dot org
2010-02-08 11:54 ` rguenth at gcc dot gnu dot org
2010-02-10 12:18 ` jingyu at google dot com [this message]
2010-02-10 13:01 ` steven at gcc dot gnu dot org
2010-02-10 13:04 ` steven at gcc dot gnu dot org
2010-02-10 16:28 ` steven at gcc dot gnu dot org
2010-02-10 17:23 ` [Bug rtl-optimization/39871] [4.3/4.4/4.5 regression] Code size increase on ARM due to poor register allocation steven at gcc dot gnu dot org
2010-02-10 17:50 ` steven at gcc dot gnu dot org
2010-02-10 19:25 ` steven at gcc dot gnu dot org
2010-02-10 22:50 ` steven at gcc dot gnu dot org
2010-02-10 23:11 ` bonzini at gnu dot org
2010-02-10 23:45 ` ramana at gcc dot gnu dot org
2010-02-10 23:47 ` steven at gcc dot gnu dot org
2010-02-10 23:53 ` steven at gcc dot gnu dot org
2010-03-18 8:29 ` steven at gcc dot gnu dot org
2010-03-18 8:31 ` steven at gcc dot gnu dot org
2010-04-06 11:38 ` rguenth at gcc dot gnu dot org
2010-06-04 12:44 ` [Bug rtl-optimization/39871] [4.3/4.4/4.5/4.6 " bernds at gcc dot gnu dot org
2010-06-17 21:52 ` bernds at gcc dot gnu dot org
2010-06-17 21:55 ` bernds at gcc dot gnu dot 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=20100210121840.26227.qmail@sourceware.org \
--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: 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).