From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: "sellcey@cavium.com" <sellcey@cavium.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Subject: Re: [Patch][aarch64] Add missing thunderx2-t99 instruction scheduling pipeline descriptions.
Date: Mon, 04 Dec 2017 17:18:00 -0000 [thread overview]
Message-ID: <5A258369.4090109@foss.arm.com> (raw)
In-Reply-To: <1512153744.14842.3.camel@cavium.com>
Hi Steve,
On 01/12/17 18:42, Steve Ellcey wrote:
> There are a number of instruction types defined in aarch64.md which do not
> have pipeline/scheduling information in thunderx2-t99.md. This patch adds
> some of them. This patch includes all the missing types except the neon
> ones that I hope to include in a follow-up patch.
>
> Bootstrapped and tested with no regressions on a thunderx2.
>
> I know we are in stage3 but I hope this type of plaform specific
> change is still OK to checkin.
>
This looks ok to me (though I cannot approve) with a style nit inline.
I'd say this fairly low risk to take in, but it's up to the maintainers
to make
the final call.
Thanks,
Kyrill
> Steve Ellcey
> sellcey@cavium.com
>
>
> 2017-11-30 Steve Ellcey <sellcey@cavium.com>
>
> * config/aarch64/thunderx2-t99.md (thunderx2t99_branch): Add trap
> to reservation.
> (thunderx2t99_nothing): New insn reservation.
> (thunderx2t99_mrs): New insn reservation.
> (thunderx2t99_multiple): New insn reservation.
> (thunderx2t99_alu_basi): Add bfx to reservation.
> (thunderx2t99_fp_cmp): Add fccmps and fccmpd to reservation.
>
>
> diff --git a/gcc/config/aarch64/thunderx2t99.md
> b/gcc/config/aarch64/thunderx2t99.md
> index 5bcf4ff..5e48521 100644
> --- a/gcc/config/aarch64/thunderx2t99.md
> +++ b/gcc/config/aarch64/thunderx2t99.md
> @@ -69,9 +69,26 @@
>
> (define_insn_reservation "thunderx2t99_branch" 1
> (and (eq_attr "tune" "thunderx2t99")
> - (eq_attr "type" "call,branch"))
> + (eq_attr "type" "call,branch,trap"))
> "thunderx2t99_i2")
>
> +;; Misc instructions.
> +
> +(define_insn_reservation "thunderx2t99_nothing" 0
> + (and (eq_attr "tune" "thunderx2t99")
> + (eq_attr "type" "no_insn,block"))
> + "nothing")
> +
> +(define_insn_reservation "thunderx2t99_mrs" 0
> + (and (eq_attr "tune" "thunderx2t99")
> + (eq_attr "type" "mrs"))
> + "thunderx2t99_i2")
> +
> +(define_insn_reservation "thunderx2t99_multiple" 1
> + (and (eq_attr "tune" "thunderx2t99")
> + (eq_attr "type" "multiple"))
> + "thunderx2t99_i0+thunderx2t99_i1+thunderx2t99_i2+thunderx2t99_ls0+thunderx2t99_ls1+thunderx2t99_sd+thunderx2t99_i1m1+thunderx2t99_i1m2+thunderx2t99_i1m3+thunderx2t99_ls0d1+thunderx2t99_ls0d2+thunderx2t99_ls0d3+thunderx2t99_ls1d1+thunderx2t99_ls1d2+thunderx2t99_ls1d3+thunderx2t99_f0+thunderx2t99_f1")
> +
We try to adhere to the 80 columns per line rule in the scheduling
description files as well,
so can you please use "\" to break this into multiple lines.
> ;; Integer arithmetic/logic instructions.
>
> ; Plain register moves are handled by renaming, and don't create any
> uops.
> @@ -87,7 +104,7 @@
> adc_reg,adc_imm,adcs_reg,adcs_imm,\
> logic_reg,logic_imm,logics_reg,logics_imm,\
> csel,adr,mov_imm,shift_reg,shift_imm,bfm,\
> - rbit,rev,extend,rotate_imm"))
> + bfx,rbit,rev,extend,rotate_imm"))
> "thunderx2t99_i012")
>
> (define_insn_reservation "thunderx2t99_alu_shift" 2
> @@ -155,7 +172,7 @@
>
> (define_insn_reservation "thunderx2t99_fp_cmp" 5
> (and (eq_attr "tune" "thunderx2t99")
> - (eq_attr "type" "fcmps,fcmpd"))
> + (eq_attr "type" "fcmps,fcmpd,fccmps,fccmpd"))
> "thunderx2t99_f01")
>
> (define_insn_reservation "thunderx2t99_fp_divsqrt_s" 16
next prev parent reply other threads:[~2017-12-04 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 18:42 Steve Ellcey
2017-12-04 17:18 ` Kyrill Tkachov [this message]
2017-12-04 17:33 ` Steve Ellcey
2017-12-05 14:39 ` James Greenhalgh
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=5A258369.4090109@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sellcey@cavium.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).