public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/64110] [5 Regression] ICE: Max. number of generated reload insns per insn is achieved (90) Date: Wed, 17 Dec 2014 08:36:00 -0000 [thread overview] Message-ID: <bug-64110-4-x1BBv7wdUc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64110-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64110 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Looking at the generated assembly, I see there: movw %di, -80(%rbp) vpbroadcastw -80(%rbp), %ymm1 vmovdqa %ymm1, -80(%rbp) I'd have expected vmovd %edi, %xmm1 vpbroadcastw %xmm1, %ymm1 vmovdqa %ymm1, -80(%rbp) Is there some bug in the *vec_dupv16hi pattern that LRA can't use the !r alternative? %di should be valid nonimmediate_operand in HImode. For e.g. typedef unsigned short V __attribute__((vector_size (32))); V foo (unsigned short x) { return (V) { x, x, x, x, x, x, x, x, x, x, x, x, x, x, x, x }; } we emit what I expect. In the latter case, at *.ira we have: (insn 2 5 3 2 (set (reg:SI 90 [ x ]) (reg:SI 5 di [ x ])) pr64110-4.c:3 90 {*movsi_internal} (expr_list:REG_DEAD (reg:SI 5 di [ x ]) (nil))) (note 3 2 4 2 NOTE_INSN_DELETED) (note 4 3 7 2 NOTE_INSN_FUNCTION_BEG) (insn 7 4 12 2 (set (reg:V16HI 92 [ D.2291 ]) (vec_duplicate:V16HI (subreg:HI (reg:SI 90 [ x ]) 0))) pr64110-4.c:4 4233 {*vec_dupv16hi} (expr_list:REG_DEAD (reg:SI 90 [ x ]) (nil))) and in the former case we have: (insn 27 36 28 2 (set (reg:SI 178 [ x ]) (reg:SI 5 di [ x ])) pr64110.c:10 90 {*movsi_internal} (expr_list:REG_DEAD (reg:SI 5 di [ x ]) (nil))) (insn 28 27 29 2 (set (reg/v:HI 177 [ x ]) (subreg:HI (reg:SI 178 [ x ]) 0)) pr64110.c:10 92 {*movhi_internal} (expr_list:REG_DEAD (reg:SI 178 [ x ]) (nil))) (note 29 28 89 2 NOTE_INSN_FUNCTION_BEG) (insn 89 29 247 2 (set (reg:V16HI 214 [ vect_cst_.21 ]) (vec_duplicate:V16HI (reg/v:HI 177 [ x ]))) 4233 {*vec_dupv16hi} (nil)) which isn't that much different...
next prev parent reply other threads:[~2014-12-17 8:36 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-29 4:25 [Bug c++/64110] New: " thiago at kde dot org 2014-11-29 4:41 ` [Bug c++/64110] " thiago at kde dot org 2014-11-29 7:17 ` thiago at kde dot org 2014-11-29 7:20 ` thiago at kde dot org 2014-11-29 13:02 ` [Bug c++/64110] [5 Regression] " hjl.tools at gmail dot com 2014-12-01 12:17 ` jakub at gcc dot gnu.org 2014-12-01 12:37 ` jakub at gcc dot gnu.org 2014-12-03 4:00 ` vmakarov at gcc dot gnu.org 2014-12-03 9:35 ` [Bug rtl-optimization/64110] " mpolacek at gcc dot gnu.org 2014-12-11 11:41 ` rguenth at gcc dot gnu.org 2014-12-12 20:11 ` vmakarov at gcc dot gnu.org 2014-12-17 3:31 ` hjl.tools at gmail dot com 2014-12-17 8:36 ` jakub at gcc dot gnu.org [this message] 2014-12-17 21:30 ` vmakarov at gcc dot gnu.org 2014-12-17 21:37 ` vmakarov at gcc dot gnu.org 2014-12-17 22:55 ` jakub at gcc dot gnu.org 2015-01-09 16:24 ` vmakarov at gcc dot gnu.org 2015-01-09 16:36 ` jakub at gcc dot gnu.org 2015-01-09 16:48 ` law at redhat dot com 2015-01-15 20:27 ` vmakarov at gcc dot gnu.org 2015-01-20 21:57 ` law at redhat 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-64110-4-x1BBv7wdUc@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).