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/64688] [4.9 Regression] internal compiler error: Max. number of generated reload insns per insn is achieved (90) Date: Fri, 27 Mar 2015 20:13:00 -0000 [thread overview] Message-ID: <bug-64688-4-c5PbvjZuF7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64688 --- Comment #19 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- Author: vmakarov Date: Fri Mar 27 19:23:15 2015 New Revision: 221743 URL: https://gcc.gnu.org/viewcvs?rev=221743&root=gcc&view=rev Log: 2015-03-27 Vladimir Makarov <vmakarov@redhat.com> Backport from mainline 2015-01-30 Vladimir Makarov <vmakarov@redhat.com> PR target/64688 * lra-constraints.c (original_subreg_reg_mode): New. (simplify_operand_subreg): Try to simplify subreg of const. Use original_subreg_reg_mode for it. (swap_operands): Update original_subreg_reg_mode. (curr_insn_transform): Set up original_subreg_reg_mode. 2015-03-27 Vladimir Makarov <vmakarov@redhat.com> Backport from mainline 2015-01-30 Vladimir Makarov <vmakarov@redhat.com> PR target/64688 * g++.dg/pr64688-2.C: New. Added: branches/gcc-4_9-branch/gcc/testsuite/g++.dg/pr64688-2.C Modified: branches/gcc-4_9-branch/gcc/ChangeLog branches/gcc-4_9-branch/gcc/lra-constraints.c branches/gcc-4_9-branch/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-03-27 19:23 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-20 12:34 [Bug target/64688] New: " trippels at gcc dot gnu.org 2015-01-20 16:50 ` [Bug target/64688] [5 Regression] " jakub at gcc dot gnu.org 2015-01-21 20:52 ` vmakarov at gcc dot gnu.org 2015-01-22 8:09 ` ubizjak at gmail dot com 2015-01-22 14:45 ` uros at gcc dot gnu.org 2015-01-22 20:26 ` uros at gcc dot gnu.org 2015-01-23 23:05 ` jakub at gcc dot gnu.org 2015-01-24 10:31 ` trippels at gcc dot gnu.org 2015-01-24 10:40 ` trippels at gcc dot gnu.org 2015-01-24 10:42 ` ubizjak at gmail dot com 2015-01-24 14:40 ` trippels at gcc dot gnu.org 2015-01-25 16:00 ` [Bug rtl-optimization/64688] " ubizjak at gmail dot com 2015-01-30 22:23 ` [Bug rtl-optimization/64688] [4.9/5 " vmakarov at gcc dot gnu.org 2015-01-31 2:48 ` law at redhat dot com 2015-01-31 7:18 ` trippels at gcc dot gnu.org 2015-01-31 8:53 ` [Bug rtl-optimization/64688] [4.9 " jakub at gcc dot gnu.org 2015-02-03 16:31 ` law at redhat dot com 2015-02-04 18:26 ` vmakarov at gcc dot gnu.org 2015-03-27 20:13 ` vmakarov at gcc dot gnu.org [this message] 2015-04-22 12:02 ` jakub at gcc dot gnu.org 2015-04-22 12:22 ` ubizjak at gmail dot com
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-64688-4-c5PbvjZuF7@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).