From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
Stam Markianos-Wright <Stam.Markianos-Wright@arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
"jlaw@ventanamicro.com" <jlaw@ventanamicro.com>
Subject: Re: [PING][PATCH 2/2] arm: Add support for MVE Tail-Predicated Low Overhead Loops
Date: Thu, 28 Sep 2023 13:51:33 +0100 [thread overview]
Message-ID: <965e9d26-5664-ccee-888c-8151b4c0abcb@arm.com> (raw)
In-Reply-To: <PAXPR08MB6926A584E7152022EE23060993F7A@PAXPR08MB6926.eurprd08.prod.outlook.com>
Hi,
On 14/09/2023 13:10, Kyrylo Tkachov via Gcc-patches wrote:
> Hi Stam,
>
>
> The arm parts look sensible but we'd need review for the df-core.h and df-core.cc changes.
> Maybe Jeff can help or can recommend someone to take a look?
> Thanks,
> Kyrill
>
FWIW the changes LGTM, if we don't want these in df-core we can always
implement the extra utility locally. It's really just a helper function
to check if df_bb_regno_first_def_find and df_bb_regno_last_def_find
yield the same result, meaning we only have a single definition.
Kind regards,
Andre
next prev parent reply other threads:[~2023-09-28 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 10:31 [PATCH " Stamatis Markianos-Wright
2023-09-06 17:19 ` [PING][PATCH " Stamatis Markianos-Wright
2023-09-14 12:10 ` Kyrylo Tkachov
2023-09-28 12:51 ` Andre Vieira (lists) [this message]
2023-10-11 11:34 ` Stamatis Markianos-Wright
2023-10-23 10:16 ` Andre Vieira (lists)
2023-10-24 15:11 ` Richard Sandiford
2023-11-06 11:03 ` Stamatis Markianos-Wright
2023-11-06 11:24 ` Richard Sandiford
2023-11-06 17:29 ` Stamatis Markianos-Wright
2023-11-10 12:41 ` Stamatis Markianos-Wright
2023-11-16 11:36 ` Stamatis Markianos-Wright
2023-11-27 12:47 ` Andre Vieira (lists)
2023-11-30 12:55 ` Stamatis Markianos-Wright
2023-12-07 18:08 ` Andre Vieira (lists)
2023-12-09 18:31 ` Richard Sandiford
2023-12-12 17:56 ` Richard Earnshaw
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=965e9d26-5664-ccee-888c-8151b4c0abcb@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Stam.Markianos-Wright@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jlaw@ventanamicro.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).