public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Andrea Corallo <andrea.corallo@arm.com>, gcc-patches@gcc.gnu.org
Cc: nd@arm.com
Subject: Re: [PATCH] [arm] Implement Armv8.1-M low overhead loops
Date: Tue, 11 Feb 2020 11:01:00 -0000	[thread overview]
Message-ID: <8468875e-934e-0bee-763d-91dd5ddbe7c9@arm.com> (raw)
In-Reply-To: <gkrmu9pxwf6.fsf@arm.com>

On 11/02/2020 10:14, Andrea Corallo wrote:
> Hi all,
> 
> This patch enables the Armv8.1-M Mainline LOB (low overhead branch) extension
> low overhead loops (LOL) feature by using the loop-doloop pass
> that it shares with the Swing Modulo Scheduler.
> 
> bootstrapped arm-none-linux-gnueabihf, does not introduce testsuite regressions.
> 
> Andrea
> 
> gcc/ChangeLog:
> 
> 2020-??-??  Andrea Corallo  <andrea.corallo@arm.com>
> 2020-??-??  Mihail-Calin Ionescu  <mihail.ionescu@arm.com>
> 2020-??-??  Iain Apreotesei  <iain.apreotesei@arm.com>
> 
>          * config/arm/arm.c (TARGET_INVALID_WITHIN_DOLOOP):
>          (arm_invalid_within_doloop): Implement invalid_within_doloop hook.
>          * config/arm/arm.h (TARGET_HAVE_LOB): Add new macro.
>          * config/arm/thumb2.md (*doloop_end, doloop_begin, dls_insn):
>          Add new patterns.
>          * config/arm/unspecs.md: Add new unspec.
> 

A date should only appear before the first author in a multi-author 
patch, other authors should then be indented to align with the name of 
that first author.

> gcc/testsuite/ChangeLog:
> 
> 2020-??-??  Andrea Corallo  <andrea.corallo@arm.com>
> 2020-??-??  Mihail-Calin Ionescu  <mihail.ionescu@arm.com>
> 2020-??-??  Iain Apreotesei  <iain.apreotesei@arm.com>
> 
>          * gcc.target/arm/lob.h: New header.
>          * gcc.target/arm/lob1.c: New testcase.
>          * gcc.target/arm/lob2.c: Likewise.
>          * gcc.target/arm/lob3.c: Likewise.
>          * gcc.target/arm/lob4.c: Likewise.
>          * gcc.target/arm/lob5.c: Likewise.
>          * gcc.target/arm/lob6.c: Likewise.
> 

+(define_insn "*doloop_end"
+  [(parallel [(set (pc)
+                   (if_then_else
+                       (ne (reg:SI LR_REGNUM) (const_int 1))
+                     (label_ref (match_operand 0 "" ""))
+                     (pc)))
+              (set (reg:SI LR_REGNUM)
+                   (plus:SI (reg:SI LR_REGNUM) (const_int -1)))])]
+  "TARGET_32BIT && TARGET_HAVE_LOB && !flag_modulo_sched"
+  "le\tlr, %l0")

Is it deliberate that this pattern name has a '*' prefix?  doloop_end is 
a named expansion pattern according to md.texi.

Also, hard-coded register names should be prefixed with '%|' (so "%|lr", 
not just "lr"), just in case the assembler dialect requires something 
(ELF doesn't but others have).  Also for dls_insn.

For the tests, your 'require-effective-taret' tests look insufficient to 
prevent problems when testing a multilib environment, you'll need (at 
least) checks that a) passing -marm has not happened and b) that the 
architecture, or a specific CPU isn't being passed on the command line.

R.

  reply	other threads:[~2020-02-11 11:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 10:15 Andrea Corallo
2020-02-11 11:01 ` Richard Earnshaw (lists) [this message]
2020-02-11 13:40   ` Andrea Corallo
2020-02-12  9:23     ` Roman Zhuykov
2020-02-13 17:54       ` Andrea Corallo
2020-02-19 13:01       ` Andrea Corallo
2020-02-21 15:31         ` Kyrill Tkachov
2020-02-21 15:49           ` Roman Zhuykov
2020-02-21 15:53             ` Kyrill Tkachov
2020-02-21 15:41         ` Roman Zhuykov
2020-02-24 15:48           ` Andrea Corallo
2020-02-25 14:57             ` Andrea Corallo

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=8468875e-934e-0bee-763d-91dd5ddbe7c9@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=andrea.corallo@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.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).