public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/58545] [4.7/4.8/4.9 Regression] error: unable to find a register to spill in class 'POINTER_REGS'
Date: Thu, 03 Oct 2013 15:32:00 -0000	[thread overview]
Message-ID: <bug-58545-4-zFWWkDRifB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58545-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58545

Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amylaar at gcc dot gnu.org

--- Comment #3 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Instruction 37 is generated by save_call_clobbered_regs.
When the eliminable registers were initialized, the frame size was
zero, and the frame pointer could be eliminated.
The frame size grew when the save area for r20 was allocated, but
reload does not update the eliminable registers in this case.
Therefore, the frame pointer r28 was eliminated to the stack pointer
in insn 37.  Thus, finding reloads and spilling finished with
insn 37 using the stack pointer and needing a POINTER_REGS reload.
Then, before it comes to selecting the reload registers, the eliminables
are updated, but not the reloads that depend on them.  Thus, we
try - unnecessarily - to reload the frame pointer, and can't because
r28 is in use as the frame pointer.


  parent reply	other threads:[~2013-10-03 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 15:48 [Bug other/58545] New: [4.7/4.8 " gjl at gcc dot gnu.org
2013-09-26 15:49 ` [Bug other/58545] " gjl at gcc dot gnu.org
2013-09-26 15:50 ` gjl at gcc dot gnu.org
2013-09-27  8:10 ` [Bug other/58545] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2013-10-03 15:32 ` amylaar at gcc dot gnu.org [this message]
2013-10-03 15:39 ` amylaar at gcc dot gnu.org
2013-10-30 23:55 ` amylaar at gcc dot gnu.org
2013-11-05 14:33 ` [Bug rtl-optimization/58545] [4.7/4.8 " rguenth at gcc dot gnu.org
2014-02-17 16:41 ` gjl at gcc dot gnu.org
2014-06-12 13:42 ` rguenth at gcc dot gnu.org
2014-12-10 12:47 ` [Bug rtl-optimization/58545] [4.8 " rguenth at gcc dot gnu.org
2014-12-19 13:24 ` jakub at gcc dot gnu.org
2015-06-23  8:42 ` 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-58545-4-zFWWkDRifB@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).