public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55247] [4.8 Regression] internal compiler error: Max. number of generated reload insns per insn is achieved (90) Date: Fri, 09 Nov 2012 19:42:00 -0000 [thread overview] Message-ID: <bug-55247-4-V0x1fNQWLG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55247-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55247 Vladimir Makarov <vmakarov at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ubizjak at gmail dot com --- Comment #2 from Vladimir Makarov <vmakarov at redhat dot com> 2012-11-09 19:42:30 UTC --- Here is the insn in question: (insn 26 25 27 2 (set (reg:TI 115 [orig:100 *defsym_17 ] [100]) (mem:TI (zero_extend:DI (reg:SI 98)) [7 *defsym_17+0 S16 A32])) h.i:54 61 {*movti_internal_rex64} As I understand the first alternative has ! to strongly encourage to use SSE instead of GENERAL registers. (define_insn "*movti_internal_rex64" [(set (match_operand:TI 0 "nonimmediate_operand" "=!r ,o ,x,x ,m") (match_operand:TI 1 "general_operand" "riFo,riF,C,xm,x"))] "TARGET_64BIT && !(MEM_P (operands[0]) && MEM_P (operands[1]))" For some reasons, the second alternative does not have !. I don't know why it is different from the first alternative. For reload it works as it already substituted hard register for the first operand and in this case it rejects the 2nd alternative. (insn 26 25 27 2 (set (reg:TI 0 ax [orig:100 *defsym_17 ] [100]) (mem:TI (zero_extend:DI (reg:SI 2 cx [98])) [7 *defsym_17+0 S16 A32])) h.i:54 61 {*movti_internal_rex64} Adding ! for the second alternative (as I believe it should be) solves the problem. (define_insn "*movti_internal_rex64" [(set (match_operand:TI 0 "nonimmediate_operand" "=!r ,!o ,x,x ,m") (match_operand:TI 1 "general_operand" "riFo,riF,C,xm,x"))] "TARGET_64BIT && !(MEM_P (operands[0]) && MEM_P (operands[1]))" Uros, is this change ok for you? If it is ok I can commit the patch only on Wednesday (I'll be away for a few days).
next prev parent reply other threads:[~2012-11-09 19:42 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-09 2:34 [Bug rtl-optimization/55247] New: " hjl.tools at gmail dot com 2012-11-09 2:34 ` [Bug rtl-optimization/55247] " hjl.tools at gmail dot com 2012-11-09 5:09 ` hjl.tools at gmail dot com 2012-11-09 19:42 ` vmakarov at redhat dot com [this message] 2012-11-10 1:32 ` hjl.tools at gmail dot com 2012-11-10 1:39 ` hjl.tools at gmail dot com 2012-11-10 1:58 ` hjl.tools at gmail dot com 2012-11-10 2:30 ` hjl.tools at gmail dot com 2012-11-10 9:15 ` ubizjak at gmail dot com 2012-11-10 9:22 ` ubizjak at gmail dot com 2012-11-10 11:28 ` uros at gcc dot gnu.org 2012-11-10 11:47 ` [Bug middle-end/55247] " ubizjak at gmail dot com 2012-11-10 11:56 ` ubizjak at gmail dot com 2012-11-10 19:02 ` [Bug rtl-optimization/55247] " hjl.tools at gmail dot com 2012-11-10 19:11 ` hjl.tools at gmail dot com 2012-11-10 19:41 ` ubizjak at gmail dot com 2012-11-11 21:53 ` ebotcazou at gcc dot gnu.org 2012-11-11 23:55 ` hjl.tools 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-55247-4-V0x1fNQWLG@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).