public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Avoid duplicate vector initializations during RTL expansion.
Date: Mon, 12 Jun 2023 16:37:50 -0600	[thread overview]
Message-ID: <a0067c3d-fd76-c57b-1a8e-ac39644a2b10@gmail.com> (raw)
In-Reply-To: <00af01d99c7f$e8a7a1e0$b9f6e5a0$@nextmovesoftware.com>



On 6/11/23 10:15, Roger Sayle wrote:
> 
> This middle-end patch avoids some redundant RTL for vector initialization
> during RTL expansion.  For the simple test case:
> 
> typedef __int128 v1ti __attribute__ ((__vector_size__ (16)));
> __int128 key;
> 
> v1ti foo() {
>      return (v1ti){key};
> }
> 
> the middle-end currently expands:
> 
> (set (reg:V1TI 85) (const_vector:V1TI [ (const_int 0) ]))
> 
> (set (reg:V1TI 85) (mem/c:V1TI (symbol_ref:DI ("key"))))
> 
> where we create a dead instruction that initializes the vector to zero,
> immediately followed by a set of the entire vector.  This patch skips
> this zeroing instruction when the vector has only a single element.
> It also updates the code to indicate when we've cleared the vector,
> so that we don't need to initialize zero elements.
> 
> Interestingly, this code is very similar to my patch from April 2006:
> https://gcc.gnu.org/pipermail/gcc-patches/2006-April/192861.html
> 
> 
> This patch has been tested on x86_64-pc-linux-gnu with a make bootstrap
> and make -k check, both with and without --target_board=unix{-m32}, with
> no new failures.  Ok for mainline?
> 
> 
> 2023-06-11  Roger Sayle  <roger@nextmovesoftware.com>
> 
> gcc/ChangeLog
>          * expr.cc (store_constructor) <case VECTOR_TYPE>: Don't bother
>          clearing vectors with only a single element.  Set CLEARED if the
>          vector was initialized to zero.
Funny how old (unresolved) issues will often raise their ugly heads again!

OK for the trunk.

jeff

      reply	other threads:[~2023-06-12 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 16:15 Roger Sayle
2023-06-12 22:37 ` Jeff Law [this message]

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=a0067c3d-fd76-c57b-1a8e-ac39644a2b10@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=roger@nextmovesoftware.com \
    /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).