public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57676] [4.8/4.9 Regression] ICE: Maximum number of LRA constraint passes is achieved (30)
Date: Wed, 30 Oct 2013 13:01:00 -0000	[thread overview]
Message-ID: <bug-57676-4-JHSppFnDmM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57676-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder if there is an algorithm to fall back to that doesn't require
iteration.
Or, if not, if we can instead check if there was progress during the last
iteration (interpreting the limit as a way to check whether we'll iterate
indefinitely).


  parent reply	other threads:[~2013-10-30 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22 15:38 [Bug rtl-optimization/57676] New: " antoine.balestrat at gmail dot com
2013-06-24 10:50 ` [Bug rtl-optimization/57676] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-06-27 16:41 ` vmakarov at gcc dot gnu.org
2013-10-16  9:51 ` jakub at gcc dot gnu.org
2013-10-30 13:01 ` rguenth at gcc dot gnu.org [this message]
2014-05-22  9:07 ` [Bug rtl-optimization/57676] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:34 ` [Bug rtl-optimization/57676] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23  8:28 ` [Bug rtl-optimization/57676] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:02 ` [Bug rtl-optimization/57676] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:32 ` jakub 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-57676-4-JHSppFnDmM@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).