public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62080] Suboptimal code generation with eigen library Date: Sun, 10 Aug 2014 11:30:00 -0000 [thread overview] Message-ID: <bug-62080-4-CqQ5BxBeJb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62080-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62080 --- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> --- (note that a minimal, self-contained testcase would be much better and shouldn't be hard to produce) We write to memory with: (insn 10 8 11 2 (set (mem:V2DI (reg/v/f:DI 97 [ vec ]) [0 MEM[(__m128i * {ref-all})vec_4(D)]+0 S16 A128]) (subreg:V2DI (reg:V4SI 98) 0)) /usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.10.0/include/emmintrin.h:706 1147 {*movv2di_internal} (expr_list:REG_DEAD (reg:V4SI 98) (nil))) and then read back with: (insn 15 12 17 2 (set (reg:V2DF 100) (vec_concat:V2DF (mem:DF (reg/v/f:DI 97 [ vec ]) [5 MEM[(const double *)vec_4(D)]+0 S8 A64]) (mem:DF (plus:DI (reg/v/f:DI 97 [ vec ]) (const_int 8 [0x8])) [0 S8 A8]))) /usr/lib/gcc-snapshot/lib/gcc/x86_64-linux-gnu/4.10.0/include/emmintrin.h:925 2016 {*vec_concatv2df} (nil)) The vec_concat of the 2 adjacent memory locations is not merged into a single memory read, although from the previous insn it looks like it is suitably aligned.
next prev parent reply other threads:[~2014-08-10 11:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-10 10:20 [Bug c++/62080] New: " beschindler at gmail dot com 2014-08-10 10:21 ` [Bug c++/62080] " beschindler at gmail dot com 2014-08-10 11:30 ` glisse at gcc dot gnu.org [this message] 2014-08-10 12:05 ` beschindler at gmail dot com 2014-08-11 19:16 ` beschindler at gmail dot com 2014-08-11 20:40 ` glisse at gcc dot gnu.org 2014-08-27 9:58 ` rguenth at gcc dot gnu.org 2020-04-06 9:43 ` [Bug middle-end/62080] " pinskia at gcc dot gnu.org 2020-04-06 10:34 ` glisse at gcc dot gnu.org 2021-07-18 21:18 ` pinskia 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-62080-4-CqQ5BxBeJb@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).