From: Evandro Menezes <e.menezes@samsung.com>
To: 'Kyrill Tkachov' <kyrylo.tkachov@arm.com>,
'Marcus Shawcroft' <Marcus.Shawcroft@arm.com>,
gcc-patches@gcc.gnu.org
Cc: 'James Greenhalgh' <James.Greenhalgh@arm.com>,
'Ramana Radhakrishnan' <Ramana.Radhakrishnan@arm.com>,
'Andrew Pinski' <pinskia@gmail.com>
Subject: RE: [PATCH][AArch64] Add separate insn sched class for vector LDP & STP
Date: Tue, 29 Sep 2015 20:55:00 -0000 [thread overview]
Message-ID: <020601d0faf5$a7186630$f5493290$@samsung.com> (raw)
In-Reply-To: <560A5367.5020604@arm.com>
It's been committed as 228253.
Thank y'all for playing.
Cheers,
--
Evandro Menezes Austin, TX
> -----Original Message-----
> From: Kyrill Tkachov [mailto:kyrylo.tkachov@arm.com]
> Sent: Tuesday, September 29, 2015 4:01
> To: Marcus Shawcroft; Evandro Menezes; gcc-patches@gcc.gnu.org
> Cc: James Greenhalgh; Ramana Radhakrishnan
> Subject: Re: [PATCH][AArch64] Add separate insn sched class for vector LDP &
> STP
>
>
> On 29/09/15 09:03, Marcus Shawcroft wrote:
> > On 29/09/15 00:52, Evandro Menezes wrote:
> >> In some micro-architectures the insns to load or store pairs of
> >> vector registers are implemented rather differently from those
> >> affecting lanes in vector registers. Then, it's important that such
> >> insns be described likewise differently in the scheduling model.
> >>
> >> This patch adds the insn types neon_ldp{,_q} and neon_stp{,_q} apart
> >> from the current neon_load2_2reg_q and neon_store2_2reg_q types,
> >> respectively.
> >>
> > Hi,
> >
> > The AArch64 part of this is OK. Please wait for Kyrill or Ramana to
> > comment on ARM side. Cheers /Marcus
> >
>
> This is ok arm-wise. I see the instructions being modelled with this type
> don't have a direct arm equivalent anyway.
> Marcus' comment on the ChangeLog still apply.
>
> Thanks,
> Kyrill
>
> >> Thank you,
> >>
> >> -- Evandro Menezes
> >>
> >>
> >> 0001-AArch64-Add-separate-insn-sched-class-for-vector-LDP.patch
> >>
> >>
> >> From 340249dcd2af8dfce486cb4f62d4eaf285c6a799 Mon Sep 17 00:00:00
> >> 2001
> >> From: Evandro Menezes<e.menezes@samsung.com>
> >> Date: Mon, 28 Sep 2015 15:00:00 -0500
> >> Subject: [PATCH] [AArch64] Add separate insn sched class for vector
> >> LDP & STP
> >>
> >> 2015-09-28 Evandro Menezes<e.menezes@samsung.com>
> >>
> >> gcc/
> >> * config/arm/types.md (neon_ldp, neon_ldp_q, neon_stp, neon_stp_q):
> >> add new insn types for vector load and store pairs.
> > s/add/Add/ and likewise the rest of the changelog comments.
> >
> >> * config/arm/cortex-a53.md (cortex_a53_f_load_2reg): add insn
> >> types "neon_ldp{,_q}".
> >> * config/arm/cortex-a57.md (neon_load_c): add insn types
> >> "neon_ldp{,_q}".
> >> (neon_store_complex): add insn types "neon_stp{,_q}".
> >> * config/aarch64/aarch64-simd.md (aarch64_be_movoi): add insn types
> >> "neon_{ldp,stp}_q".
next prev parent reply other threads:[~2015-09-29 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 5:39 Evandro Menezes
2015-09-29 6:29 ` Andrew Pinski
2015-09-29 9:01 ` Marcus Shawcroft
2015-09-29 10:00 ` Kyrill Tkachov
2015-09-29 20:55 ` Evandro Menezes [this message]
2015-09-30 2:50 ` Ramana Radhakrishnan
2015-10-01 15:40 ` Evandro Menezes
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='020601d0faf5$a7186630$f5493290$@samsung.com' \
--to=e.menezes@samsung.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=pinskia@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).