public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Oluwatamilore Adebayo <oluwatamilore.adebayo@arm.com>
To: <richard.sandiford@arm.com>
Cc: <Oluwatamilore.Adebayo@arm.com>, <gcc-patches@gcc.gnu.org>,
	<richard.guenther@gmail.com>
Subject: Re: [PATCH] rtl: AArch64: New RTL for ABD
Date: Tue, 6 Jun 2023 16:11:53 +0100	[thread overview]
Message-ID: <20230606151153.53653-1-oluwatamilore.adebayo@arm.com> (raw)
In-Reply-To: <mptwn18zcf5.fsf@arm.com>

> It would be good to mark all of these functions with __attribute__((noipa)),
> since I think interprocedural optimisations might otherwise defeat the
> runtime test in abd_run_1.c (in the sense that we might end up folding
> things at compile time and not testing the vector versions of the functions).

Done.

> There are 14 tests, and it looks like 6 of them are expected to produce
> ABD instructions while 8 aren't.  It isn't really clear which tests are
> which though.
> 
> I think it'd help to split the file into two:
> 
> - one containing only the tests that should produce ABD, so that the
>   scan-assembler counts sum up to the number of tests
> 
> - one containing only the tests that cannot use ABD, with:
> 
>     { dg-final { scan-assembler-not {\tsabd\t} } }
>     { dg-final { scan-assembler-not {\tuabd\t} } }
> 
>   to enforce that

After adjustments made to the vectoriser part, all tests now use an abd
instruction.

> For these SVE tests, it'd be better to drop the:
> 
>   #pragma GCC target "arch=armv8-a"
> 
> lines and instead allow SVE to be used as normal.  We should then be
> able to match the SVE instructions in the dg-final lines.

Done, and changed the assembler scans to reflect this.

Patch is in the next response.

  reply	other threads:[~2023-06-06 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 16:14 Oluwatamilore Adebayo
2023-05-16 12:30 ` Richard Sandiford
2023-06-06 15:11   ` Oluwatamilore Adebayo [this message]
2023-06-06 15:17     ` [PATCH 2/2] " Oluwatamilore Adebayo
2023-06-06 17:03     ` [PATCH] rtl: " Richard Sandiford
2023-06-08 10:37       ` Oluwatamilore Adebayo
2023-06-08 10:38         ` [PATCH 2/2] " Oluwatamilore Adebayo
2023-06-13  8:27           ` Oluwatamilore Adebayo

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=20230606151153.53653-1-oluwatamilore.adebayo@arm.com \
    --to=oluwatamilore.adebayo@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=richard.sandiford@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).