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/60040] AVR: error: unable to find a register to spill in class 'POINTER_REGS'
Date: Mon, 17 Mar 2014 12:38:00 -0000 [thread overview]
Message-ID: <bug-60040-4-UFjgGppRYo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60040-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60040
Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amylaar at gcc dot gnu.org
--- Comment #5 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
Created attachment 32372
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32372&action=edit
tentative patch for tentative reloads
In this case, reload already knows that it has to re-do the reloads, but it
goes ahead anyway and computes reloads registers for this iteration.
Unfortunately, when find_reload_regs fails, it then calls spill_failure,
giving a hard error for a reload that we don't need in the first place.
The patch in this attachment passes down something_changed from reload
as tentative to select_reload_regs and then on to find_reload_regs to
not worry about the failure.
Also, in reload, I made it not 'goto failure' in that case.
next prev parent reply other threads:[~2014-03-17 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 11:13 [Bug target/60040] New: " sebastian.huber@embedded-brains.de
2014-02-03 11:13 ` [Bug target/60040] " sebastian.huber@embedded-brains.de
2014-02-17 16:41 ` [Bug other/60040] " gjl at gcc dot gnu.org
2014-02-18 8:12 ` sebastian.huber@embedded-brains.de
2014-02-18 10:35 ` gjl at gcc dot gnu.org
2014-02-18 10:50 ` gjl at gcc dot gnu.org
2014-03-17 12:38 ` amylaar at gcc dot gnu.org [this message]
2014-04-07 13:19 ` sebastian.huber@embedded-brains.de
2014-11-05 16:19 ` joel at gcc dot gnu.org
2015-10-13 12:55 ` matthijs at stdin dot nl
2015-10-13 12:56 ` matthijs at stdin dot nl
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-60040-4-UFjgGppRYo@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).