public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Kito Cheng <kito.cheng@gmail.com>
Cc: christoph.muellner@vrull.eu, gcc-patches@gcc.gnu.org,
	kito.cheng@sifive.com, Jim Wilson <jim.wilson.gcc@gmail.com>,
	Andrew Waterman <andrew@sifive.com>,
	philipp.tomsich@vrull.eu, jeffreyalaw@gmail.com,
	Vineet Gupta <vineetg@rivosinc.com>
Subject: Re: [PATCH 7/7] riscv: Add support for str(n)cmp inline expansion
Date: Mon, 14 Nov 2022 16:53:20 -0800 (PST)	[thread overview]
Message-ID: <mhng-b7fb073e-8f95-4fa7-a544-e295165ed9c1@palmer-ri-x1c9a> (raw)
In-Reply-To: <CA+yXCZDgXLQOKE4cY+=AELQeimiQY7_uPvcwjXOKeR=ifqZJ4A@mail.gmail.com>

On Mon, 14 Nov 2022 16:46:37 PST (-0800), Kito Cheng wrote:
> Hi Christoph:
>
>> This patch implements expansions for the cmpstrsi and the cmpstrnsi
>> builtins using Zbb instructions (if available).
>> This allows to inline calls to strcmp() and strncmp().
>>
>> The expansion basically emits a peeled comparison sequence (i.e. a peeled
>> comparison loop) which compares XLEN bits per step if possible.
>>
>> The emitted sequence can be controlled, by setting the maximum number
>> of compared bytes (-mstring-compare-inline-limit).
>
> I would like to have a unified option interface,
> maybe -m[no-]inline-str[n]cmp and -minline-str[n]cmp-limit.
> And add some option like this:
> -minline-str[n]cmp=[bitmanip|vector|auto] in future,
> since I assume we'll have different versions of those things.

Can we just decide that from mtune?  We'll probably have uarch-specific 
string functions at some point, might as well start planning for it now.

>> gcc/ChangeLog:
>>
>>         * config/riscv/riscv-protos.h (riscv_expand_strn_compare): New
>>           prototype.
>>         * config/riscv/riscv-string.cc (GEN_EMIT_HELPER3): New helper
>>           macros.
>>         (GEN_EMIT_HELPER2): New helper macros.
>>         (expand_strncmp_zbb_sequence): New function.
>>         (riscv_emit_str_compare_zbb): New function.
>>         (riscv_expand_strn_compare): New function.
>>         * config/riscv/riscv.md (cmpstrnsi): Invoke expansion functions
>>           for strn_compare.
>>         (cmpstrsi): Invoke expansion functions for strn_compare.
>>         * config/riscv/riscv.opt: Add new parameter
>>           '-mstring-compare-inline-limit'.
>
> We need to document this option.

  reply	other threads:[~2022-11-15  0:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 23:05 [PATCH 0/7] riscv: Improve builtins expansion Christoph Muellner
2022-11-13 23:05 ` [PATCH 1/7] riscv: bitmanip: add orc.b as an unspec Christoph Muellner
2022-11-14 16:51   ` Jeff Law
2022-11-14 17:53     ` Jeff Law
2022-11-14 19:05     ` Philipp Tomsich
2022-11-13 23:05 ` [PATCH 2/7] riscv: bitmanip/zbb: Add prefix/postfix and enable visiblity Christoph Muellner
2022-11-14 16:55   ` Jeff Law
2022-11-13 23:05 ` [PATCH 3/7] riscv: Enable overlap-by-pieces via tune param Christoph Muellner
2022-11-14  2:48   ` Vineet Gupta
2022-11-14  7:59     ` Philipp Tomsich
2022-11-14  8:29       ` Christoph Müllner
2022-11-14 19:04         ` Jeff Law
2022-11-14 19:07           ` Christoph Müllner
2022-11-13 23:05 ` [PATCH 4/7] riscv: Move riscv_block_move_loop to separate file Christoph Muellner
2022-11-14 16:56   ` Jeff Law
2022-11-13 23:05 ` [PATCH 5/7] riscv: Use by-pieces to do overlapping accesses in block_move_straight Christoph Muellner
2022-11-14 17:16   ` Jeff Law
2022-11-14 19:01     ` Christoph Müllner
2022-11-14 19:05       ` Jeff Law
2022-11-13 23:05 ` [PATCH 6/7] riscv: Add support for strlen inline expansion Christoph Muellner
2022-11-14 18:17   ` Jeff Law
2022-11-14 21:07     ` Christoph Müllner
2022-11-13 23:05 ` [PATCH 7/7] riscv: Add support for str(n)cmp " Christoph Muellner
2022-11-14 19:28   ` Jeff Law
2022-11-14 21:49     ` Christoph Müllner
2022-11-15  0:22       ` Jeff Law
2022-11-15  0:46   ` Kito Cheng
2022-11-15  0:53     ` Palmer Dabbelt [this message]
2022-11-15  1:55       ` Kito Cheng
2022-11-15  3:41       ` Jeff Law
2022-11-15 22:22     ` Christoph Müllner
2022-11-16  0:15     ` Philipp Tomsich
2022-11-21  3:24       ` Kito Cheng

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=mhng-b7fb073e-8f95-4fa7-a544-e295165ed9c1@palmer-ri-x1c9a \
    --to=palmer@dabbelt.com \
    --cc=andrew@sifive.com \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=kito.cheng@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=vineetg@rivosinc.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).