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 middle-end/55266] vector expansion: 36 movs for 4 adds
Date: Tue, 13 Nov 2012 10:23:00 -0000	[thread overview]
Message-ID: <bug-55266-4-OnmdLGe7iY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55266-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55266

--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> 2012-11-13 10:23:03 UTC ---
The first copy is PR 52436.

The second copy has a patch posted here:
http://gcc.gnu.org/ml/gcc-patches/2012-11/msg00900.html

The last copy would require turning:

  gimple_assign <constructor, _5, {_15, _18}, NULL, NULL>
  gimple_assign <ssa_name, *x_2(D), _5, NULL, NULL>

into:

  gimple_assign <ssa_name, *x_2(D), _15, NULL, NULL>
  gimple_assign <ssa_name, MEM[(vec *)x_2(D) + 16B], _18, NULL, NULL>

(not sure if endianness matters here)

which could maybe more easily be done by splitting the memory write (when the
vector type is not supported) into a suitable number of bit_field_ref
extractions and memory writes and relying on forwprop4 to simplify the
bit_field_refs of the constructor.


  reply	other threads:[~2012-11-13 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 15:10 [Bug middle-end/55266] New: " glisse at gcc dot gnu.org
2012-11-13 10:23 ` glisse at gcc dot gnu.org [this message]
2012-11-28 10:11 ` [Bug middle-end/55266] " glisse at gcc dot gnu.org
2012-12-09  2:08 ` [Bug middle-end/55266] vector expansion: 24 " pinskia at gcc dot gnu.org
2013-03-03 11:58 ` vincenzo.innocente at cern dot ch
2023-07-21 12:12 ` rguenth 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-55266-4-OnmdLGe7iY@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: link
Be 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).