From: "H.J. Lu" <hjl.tools@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>, Jeffrey Law <law@redhat.com>,
Jakub Jelinek <jakub@redhat.com>,
Richard Guenther <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Eric Botcazou <ebotcazou@libertysurf.fr>
Subject: PING^2: [PATCH] apply_subst_iterator: Handle define_split/define_insn_and_split
Date: Tue, 13 Nov 2018 14:09:00 -0000 [thread overview]
Message-ID: <CAMe9rOreNdGDAaGXagA45CdTsZ+Z03HfQ1=EcUDqkR_nQg2qwA@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOr55FrKORUxpy8MZfApkjoCF8HRGRP7ocN9QxxArjQx7w@mail.gmail.com>
On Sun, Nov 4, 2018 at 7:24 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Fri, Oct 26, 2018 at 12:44 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> >
> > On 10/25/18, Uros Bizjak <ubizjak@gmail.com> wrote:
> > > On Fri, Oct 26, 2018 at 8:48 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >>
> > >> On 10/25/18, Uros Bizjak <ubizjak@gmail.com> wrote:
> > >> > On Fri, Oct 26, 2018 at 8:07 AM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >> >>
> > >> >> * read-rtl.c (apply_subst_iterator): Handle
> > >> >> define_insn_and_split.
> > >> >> ---
> > >> >> gcc/read-rtl.c | 6 ++++--
> > >> >> 1 file changed, 4 insertions(+), 2 deletions(-)
> > >> >>
> > >> >> diff --git a/gcc/read-rtl.c b/gcc/read-rtl.c
> > >> >> index d698dd4af4d..5957c29671a 100644
> > >> >> --- a/gcc/read-rtl.c
> > >> >> +++ b/gcc/read-rtl.c
> > >> >> @@ -275,9 +275,11 @@ apply_subst_iterator (rtx rt, unsigned int, int
> > >> >> value)
> > >> >> if (value == 1)
> > >> >> return;
> > >> >> gcc_assert (GET_CODE (rt) == DEFINE_INSN
> > >> >> + || GET_CODE (rt) == DEFINE_INSN_AND_SPLIT
> > >> >> || GET_CODE (rt) == DEFINE_EXPAND);
> > >> >
> > >> > Can we also handle DEFINE_SPLIT here?
> > >> >
> > >>
> > >> Yes, we could if there were a usage for it. I am reluctant to add
> > >> something
> > >> I have no use nor test for.
> > >
> > > Just split one define_insn_and_split to define_insn and corresponding
> > > define_split.
> > >
> > > define_insn_and_split is a contraction for for the define_insn and
> > > corresponding define_split, so it looks weird to only handle
> > > define_insn_and-split without handling define_split.
> > >
> >
> > Here is the updated patch to handle define_split. Tested with
> >
> > (define_insn "*sse4_1_<code>v8qiv8hi2<mask_name>_2"
> > [(set (match_operand:V8HI 0 "register_operand")
> > (any_extend:V8HI
> > (vec_select:V8QI
> > (subreg:V16QI
> > (vec_concat:V2DI
> > (match_operand:DI 1 "memory_operand")
> > (const_int 0)) 0)
> > (parallel [(const_int 0) (const_int 1)
> > (const_int 2) (const_int 3)
> > (const_int 4) (const_int 5)
> > (const_int 6) (const_int 7)]))))]
> > "TARGET_SSE4_1 && <mask_avx512bw_condition> && <mask_avx512vl_condition>"
> > "#")
> >
> > (define_split
> > [(set (match_operand:V8HI 0 "register_operand")
> > (any_extend:V8HI
> > (vec_select:V8QI
> > (subreg:V16QI
> > (vec_concat:V2DI
> > (match_operand:DI 1 "memory_operand")
> > (const_int 0)) 0)
> > (parallel [(const_int 0) (const_int 1)
> > (const_int 2) (const_int 3)
> > (const_int 4) (const_int 5)
> > (const_int 6) (const_int 7)]))))]
> > "TARGET_SSE4_1 && <mask_avx512bw_condition> && <mask_avx512vl_condition>
> > && can_create_pseudo_p ()"
> > [(set (match_dup 0)
> > (any_extend:V8HI (match_dup 1)))]
> > {
> > operands[1] = adjust_address_nv (operands[1], V8QImode, 0);
> > })
> >
>
> PING:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-10/msg01665.html
>
> This patch blocks an i386 backend patch.
>
PING.
--
H.J.
next prev parent reply other threads:[~2018-11-13 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 8:42 H.J. Lu
2018-11-04 15:25 ` PING: " H.J. Lu
2018-11-13 14:09 ` H.J. Lu [this message]
2018-11-20 17:09 ` PING^3: " H.J. Lu
2018-11-21 8:50 ` Richard Biener
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='CAMe9rOreNdGDAaGXagA45CdTsZ+Z03HfQ1=EcUDqkR_nQg2qwA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
--cc=ubizjak@gmail.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).