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] Code size increase of +10% between two 4.7.1 snapshot
Date: Wed, 06 Jun 2012 20:05:00 -0000 [thread overview]
Message-ID: <bug-53595-4-PA4SJk2dNT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53595-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53595
--- Comment #6 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-06-06 20:05:02 UTC ---
And here is the first part of the diff of the reload dumps that shows that
something weird is going on:
--- bresenham-i-1.198r.reload Wed Jun 6 19:59:24 2012
+++ bresenham-i-2.198r.reload Wed Jun 6 19:59:26 2012
@@ -273,123 +273,378 @@
changing reg in insn 251
changing reg in insn 249
changing reg in insn 252
+Spilling for insn 40.
+Using reg 30 for reload 0
+Spilling for insn 44.
+Using reg 26 for reload 0
+Spilling for insn 45.
+Using reg 28 for reload 0
Spilling for insn 65.
+Using reg 28 for reload 0
Spilling for insn 68.
+Using reg 28 for reload 0
Spilling for insn 71.
+Using reg 28 for reload 0
Spilling for insn 75.
+Using reg 28 for reload 0
Spilling for insn 76.
+Using reg 28 for reload 0
Spilling for insn 78.
+Using reg 26 for reload 0
+Spilling for insn 248.
+Using reg 30 for reload 0
+Spilling for insn 249.
+Using reg 30 for reload 0
Spilling for insn 202.
+Using reg 30 for reload 0
Spilling for insn 203.
+Using reg 30 for reload 0
+Spilling for insn 96.
+Using reg 30 for reload 0
+Spilling for insn 204.
+Using reg 30 for reload 0
+Spilling for insn 205.
+Using reg 30 for reload 0
+Spilling for insn 108.
+Using reg 28 for reload 0
+Spilling for insn 112.
+Using reg 28 for reload 0
+Spilling for insn 114.
+Using reg 28 for reload 0
Spilling for insn 142.
+Using reg 28 for reload 0
Spilling for insn 143.
+Using reg 30 for reload 0
Spilling for insn 144.
+Using reg 30 for reload 0
Spilling for insn 145.
+Using reg 30 for reload 0
Spilling for insn 146.
+Using reg 30 for reload 0
+Spilling for insn 154.
+Using reg 30 for reload 0
+Spilling for insn 159.
+Using reg 30 for reload 0
+Spilling for insn 165.
+Using reg 30 for reload 0
+Spilling for insn 170.
+Using reg 30 for reload 0
Spilling for insn 176.
+Using reg 30 for reload 0
Spilling for insn 179.
+Using reg 30 for reload 0
+Spilling for insn 40.
+Using reg 30 for reload 0
+Spilling for insn 44.
+Using reg 26 for reload 0
+Spilling for insn 45.
+Using reg 28 for reload 0
+Spilling for insn 65.
+Using reg 28 for reload 0
+Spilling for insn 68.
+Using reg 28 for reload 0
+Spilling for insn 71.
+Using reg 28 for reload 0
+Spilling for insn 75.
+Using reg 28 for reload 0
+Spilling for insn 76.
+Using reg 28 for reload 0
+Spilling for insn 78.
+Using reg 26 for reload 0
+Spilling for insn 248.
+Using reg 30 for reload 0
+Spilling for insn 249.
+Using reg 30 for reload 0
+Spilling for insn 202.
+Using reg 30 for reload 0
+Spilling for insn 203.
+Using reg 30 for reload 0
+Spilling for insn 96.
+Using reg 30 for reload 0
+Spilling for insn 204.
+Using reg 30 for reload 0
+Spilling for insn 205.
+Using reg 30 for reload 0
+Spilling for insn 108.
+Using reg 28 for reload 0
+Spilling for insn 112.
+Using reg 28 for reload 0
+Spilling for insn 114.
+Using reg 28 for reload 0
+Spilling for insn 142.
+Using reg 28 for reload 0
+Spilling for insn 143.
+Using reg 30 for reload 0
+Spilling for insn 144.
+Using reg 30 for reload 0
+Spilling for insn 145.
+Using reg 30 for reload 0
+Spilling for insn 146.
+Using reg 30 for reload 0
+Spilling for insn 154.
+Using reg 30 for reload 0
+Spilling for insn 159.
+Using reg 30 for reload 0
+Spilling for insn 165.
+Using reg 30 for reload 0
+Spilling for insn 170.
+Using reg 30 for reload 0
+Spilling for insn 176.
+Using reg 30 for reload 0
+Spilling for insn 179.
+Using reg 30 for reload 0
next prev parent reply other threads:[~2012-06-06 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 19:53 [Bug rtl-optimization/53595] New: " gjl at gcc dot gnu.org
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 [this message]
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-PA4SJk2dNT@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: 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).