public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Alexander Monakov <amonakov@ispras.ru>,
	Noah Goldstein <goldstein.w.n@gmail.com>
Cc: James Tirta Halim <tirtajames45@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v6] sysdeps/x86_64/multiarch/memmem-avx2.c: add memmem-avx2.c
Date: Mon, 19 Feb 2024 11:25:09 -0300	[thread overview]
Message-ID: <9afb9731-416c-4d80-814b-0f9eb4e024ab@linaro.org> (raw)
In-Reply-To: <81a6a505-b2d0-6deb-064a-08ed0e6ff226@ispras.ru>



On 19/02/24 05:13, Alexander Monakov wrote:
> 
> On Mon, 19 Feb 2024, Noah Goldstein wrote:
> 
>> It doesn't seem you have addressed many of the comments from your v5 patch.
>> Can it helps if you
>> 1: Reply to the comments indicating they are handled / why are choosing not
>> to handle them.
>> 2: Send further versions to the same email chain. (`--in-reply-to`
>> with `git send-email`).
> 
> Are you ok with the change in worst-case time complexity? The existing generic
> implementation is O(n+m), the proposed variants are O(n*m).

I think we should consider this a regression, we already have a bug opened for
wcsstr [1] for a similar issue. We already had another similar issue for
PowerPC [2], and we did not have consensus back then because the generic
implementation was also O(m*n) (it was before Wilco new implementation).

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=23865
[2] https://sourceware.org/pipermail/libc-alpha/2015-July/062808.html

  reply	other threads:[~2024-02-19 14:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18  8:26 James Tirta Halim
2024-02-19  0:07 ` Noah Goldstein
2024-02-19  8:13   ` Alexander Monakov
2024-02-19 14:25     ` Adhemerval Zanella Netto [this message]
2024-02-19 17:20       ` Noah Goldstein
2024-02-20  3:00         ` James
2024-02-20 14:30           ` Adhemerval Zanella Netto
2024-02-20 15:16             ` James
2024-02-20 16:13               ` Noah Goldstein
2024-02-20 16:26                 ` James
2024-02-20 16:38                   ` Noah Goldstein
2024-02-21  6:57 ` [PATCH v7] " James Tirta Halim
2024-02-21 17:17   ` Noah Goldstein
2024-02-21 20:30     ` Alexander Monakov
2024-02-21 22:17       ` Noah Goldstein
2024-02-23 17:27         ` Adhemerval Zanella Netto
2024-02-29 20:19           ` Alexander Monakov
2024-03-02 21:00             ` Noah Goldstein
2024-03-05 15:25             ` Adhemerval Zanella Netto
2024-03-05 17:05               ` Noah Goldstein
2024-02-27 15:06       ` Rich Felker
2024-03-01 21:31         ` Gabriel Ravier
2024-02-24  4:25     ` James
2024-02-24  9:09   ` [PATCH v8] " James Tirta Halim
2024-02-24  9:29   ` James Tirta Halim

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=9afb9731-416c-4d80-814b-0f9eb4e024ab@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=amonakov@ispras.ru \
    --cc=goldstein.w.n@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=tirtajames45@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).