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/65078] [5 Regression] 4.9 and 5.0 generate more spill-fill in comparison with 4.8.2 Date: Tue, 17 Mar 2015 11:05:00 -0000 [thread overview] Message-ID: <bug-65078-4-Fc1Jcg104E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65078-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65078 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |uros at gcc dot gnu.org --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So, in *.optimized the changes are just 16 times a difference like: - _62 = __builtin_ia32_vec_ext_v2di (_63, 0); + _62 = BIT_FIELD_REF <_63, 64, 0>; And during expansion, the difference is: -;; _62 = __builtin_ia32_vec_ext_v2di (_63, 0); - -(insn 42 41 43 (set (reg:V2DI 329) - (subreg:V2DI (reg:V16QI 138 [ D.4823 ]) 0)) ./include/emmintrin.h:722 -1 - (nil)) - -(insn 43 42 44 (set (reg:DI 330) - (vec_select:DI (reg:V2DI 329) - (parallel [ - (const_int 0 [0]) - ]))) ./include/emmintrin.h:722 -1 - (nil)) - -(insn 44 43 0 (set (reg:DI 136 [ D.4825 ]) - (reg:DI 330)) ./include/emmintrin.h:722 -1 - (nil)) - -;; MEM[(long long int *)dest_268] = _62; - -(insn 45 44 0 (set (mem:DI (reg/v/f:SI 317 [ dest ]) [3 MEM[(long long int *)dest_268]+0 S8 A64]) - (reg:DI 136 [ D.4825 ])) ./include/emmintrin.h:722 -1 - (nil)) +;; MEM[(long long int *)dest_268] = _62; + +(insn 42 41 43 (set (reg:TI 329) + (subreg:TI (reg:V16QI 138 [ D.4825 ]) 0)) ./include/emmintrin.h:722 -1 + (nil)) +(insn 43 42 0 (set (mem:DI (reg/v/f:SI 317 [ dest ]) [3 MEM[(long long int *)dest_268]+0 S8 A64]) + (subreg:DI (reg:TI 329) 0)) ./include/emmintrin.h:722 -1 + (nil)) With the new storel_epi64 we get before RA: (insn 43 40 44 3 (set (mem:DI (reg/v/f:SI 317 [ dest ]) [3 MEM[(long long int *)dest_268]+0 S8 A64]) (subreg:DI (reg:V16QI 328) 0)) ./include/emmintrin.h:722 89 {*movdi_internal} (expr_list:REG_DEAD (reg:V16QI 328) (nil))) out of this, and not surprisingly the RA reloads it by storing the V16QI 328 into stack and loads back a DImode value, while with the old intrinsic before RA we have: (insn 45 43 46 3 (set (mem:DI (reg/v/f:SI 317 [ dest ]) [3 MEM[(long long int *)dest_268]+0 S8 A64]) (vec_select:DI (subreg:V2DI (reg:V16QI 328) 0) (parallel [ (const_int 0 [0]) ]))) ./include/emmintrin.h:722 3660 {*vec_extractv2di_0_sse} (expr_list:REG_DEAD (reg:V16QI 328) (nil))) and don't need to spill that. Now the question is if we can tell RA somehow (secondary reload) that to get a DImode lowpart subreg (and SImode too?) out of a vector register it can use the *vec_extractv2di_0_sse instruction for that. Or add !TARGET_64BIT pattern for storing a DImode lowpart subreg of a vector register (any mode there?) into memory? Or ensure that the BIT_FIELD_REF is expanded as the builtin used to be.
next prev parent reply other threads:[~2015-03-17 11:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-16 14:17 [Bug rtl-optimization/65078] New: [5.0 " ysrumyan at gmail dot com 2015-02-16 14:19 ` [Bug rtl-optimization/65078] " ysrumyan at gmail dot com 2015-02-16 14:38 ` rguenth at gcc dot gnu.org 2015-02-16 14:40 ` ubizjak at gmail dot com 2015-02-16 14:44 ` rguenth at gcc dot gnu.org 2015-02-16 14:44 ` jakub at gcc dot gnu.org 2015-02-16 14:50 ` jakub at gcc dot gnu.org 2015-02-18 17:15 ` [Bug rtl-optimization/65078] [5 " law at redhat dot com 2015-03-17 10:33 ` jakub at gcc dot gnu.org 2015-03-17 11:05 ` jakub at gcc dot gnu.org [this message] 2015-03-17 12:22 ` jakub at gcc dot gnu.org 2015-03-17 15:13 ` jakub at gcc dot gnu.org 2015-03-18 10:59 ` jakub at gcc dot gnu.org 2015-03-18 11:12 ` 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-65078-4-Fc1Jcg104E@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).