public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
	Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] vect: Add a popcount fallback.
Date: Tue, 8 Aug 2023 08:14:20 -0600	[thread overview]
Message-ID: <d95369e6-09f1-f192-737b-6bb9e842e1ab@gmail.com> (raw)
In-Reply-To: <ece96a4d-692f-1d75-e54e-eae958c6aaca@gmail.com>



On 8/8/23 02:55, Robin Dapp via Gcc-patches wrote:
>> Looks reasonable to me - I couldn't read from above whether you did
>> testing on riscv and thus verified the runtime correctness of the fallback?
>> If not may I suggest to force matching the pattern on a target you can
>> test for this purpose?
> 
> I tested on riscv (manually and verified the run test) but didn't bootstrap.
> The vector test suite (or autovec) is not yet enabled by default anyway but
> that's going to change soon.
Presumably this is an alternative to the approach Juzhe posted a week or 
two ago and ultimately dropped?


Jeff

  parent reply	other threads:[~2023-08-08 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 20:20 Robin Dapp
2023-08-08  6:21 ` Richard Biener
2023-08-08  8:55   ` Robin Dapp
2023-08-08 10:02     ` Richard Biener
2023-08-08 11:37       ` Robin Dapp
2023-08-08 12:49         ` Richard Biener
2023-08-08 13:06           ` Robin Dapp
2023-08-08 13:28             ` Richard Biener
2023-08-09 10:23               ` Robin Dapp
2023-08-09 11:58                 ` Richard Biener
2023-08-08 14:14     ` Jeff Law [this message]
2023-08-08 14:21       ` Robin Dapp

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=d95369e6-09f1-f192-737b-6bb9e842e1ab@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdapp.gcc@gmail.com \
    --cc=richard.guenther@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).