public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/53595] New: Code size increase of +10% between two 4.7.1 snapshot Date: Wed, 06 Jun 2012 19:53:00 -0000 [thread overview] Message-ID: <bug-53595-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53595 Bug #: 53595 Summary: Code size increase of +10% between two 4.7.1 snapshot Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: gjl@gcc.gnu.org Created attachment 27568 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27568 C source This problem report is about a +10% of code size increase between the following two 4.7.1 versions of gcc: V1: SVN 185693 gcc-4_7-branch from 2012-03-22, 4.7.1 (prerelease) V2: SVN 188257 gcc-4_7-branch from 2012-06-06, 4.7.1 (prerelease) The attached test case is a reduced test case out of many other sources that suffer from the same problem, so that the overall performance degradation is unpleasant. The RTL dumps show that the first pass that differs is IRA. == Command line == $ avr-gcc -mmcu=atmega168 -c -std=gnu99 -Os -mstrict-X -ffixed-2 -ffixed-3 -dp -fdump-rtl-ira-details -fdump-rtl-reload-details -fdump-rtl-postreload-details bresenham-i.c -o bresenham-i-1.o -save-temps=obj resp. with -o bresenham-i-2.o for the second 4.7.1 snapshot. == GCC configure == Target: avr Configured with: ../../gcc.gnu.org/gcc-4_7-branch/configure --target=avr --prefix=/local/gnu/install/gcc-4.7-mingw32 --host=i386-mingw32 --build=i686-linux-gnu --enable-languages=c,c++ --disable-nls --disable-shared --with-dwarf2 Thread model: single gcc version 4.7.1 20120606 (prerelease) (GCC) GNU C (GCC) version 4.7.1 20120606 (prerelease) (avr) compiled by GNU C version 3.4.5 (mingw-vista special r2), GMP version 4.3.2, MPFR version 2.4.2, MPC version 0.8.2 It's a canadian cross, but that surely does not matter here...
next reply other threads:[~2012-06-06 19:53 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-06 19:53 gjl at gcc dot gnu.org [this message] 2012-06-06 19:54 ` [Bug rtl-optimization/53595] " gjl at gcc dot gnu.org 2012-06-06 19:56 ` gjl at gcc dot gnu.org 2012-06-06 19:57 ` gjl at gcc dot gnu.org 2012-06-06 19:58 ` gjl at gcc dot gnu.org 2012-06-06 20:01 ` jakub at gcc dot gnu.org 2012-06-06 20:05 ` gjl at gcc dot gnu.org 2012-06-06 20:12 ` gjl at gcc dot gnu.org 2012-06-07 13:25 ` gjl at gcc dot gnu.org 2012-06-07 13:27 ` gjl at gcc dot gnu.org 2012-06-07 13:31 ` gjl at gcc dot gnu.org 2012-06-08 17:04 ` gjl at gcc dot gnu.org 2012-06-28 13:54 ` gjl at gcc dot gnu.org 2012-06-28 13:58 ` gjl at gcc dot gnu.org 2012-06-28 14:02 ` [Bug other/53595] " gjl 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-53595-4@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).