public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63448] [4.9/5 Regression] ICE when compiling atlas 3.10.2 Date: Wed, 15 Oct 2014 15:15:00 -0000 [thread overview] Message-ID: <bug-63448-4-JFMU5bjc7g@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63448-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63448 --- Comment #8 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- I already saw such problem. It is chain of spills and reassignment of non-reload pseudos. Each pass considers only 1-2 pseudos and very few insns. We just need 2 more passes to finish RA for the test. The current code of LRA looping prevention is too conservative for the case. Finally I have an idea how to solve this kind of problems. The patch is on the way.
next prev parent reply other threads:[~2014-10-15 15:15 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-03 6:42 [Bug c/63448] New: " svante.signell at gmail dot com 2014-10-03 6:48 ` [Bug c/63448] " svante.signell at gmail dot com 2014-10-03 6:56 ` svante.signell at gmail dot com 2014-10-03 7:00 ` trippels at gcc dot gnu.org 2014-10-03 7:02 ` pinskia at gcc dot gnu.org 2014-10-06 14:57 ` [Bug rtl-optimization/63448] " rguenth at gcc dot gnu.org 2014-10-06 18:52 ` [Bug rtl-optimization/63448] [4.9/5 Regression] " jakub at gcc dot gnu.org 2014-10-15 15:15 ` vmakarov at gcc dot gnu.org [this message] 2014-10-15 15:49 ` vmakarov at gcc dot gnu.org 2014-10-15 15:51 ` vmakarov at gcc dot gnu.org 2014-10-23 10:34 ` 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-63448-4-JFMU5bjc7g@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).