public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at gms dot tf" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88545] std::find compile to memchr in trivial random access cases (patch)
Date: Tue, 14 May 2024 22:33:53 +0000	[thread overview]
Message-ID: <bug-88545-4-e1WYGsZZdL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88545-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545

--- Comment #4 from Georg Sauthoff <gcc at gms dot tf> ---
Sam, thank you for the hint and surfacing it again.

(In reply to Jonathan Wakely from comment #2)
[..]
> I would prefer to do simply:
[..]

Yes, please go ahead with your approach.


> I think we're going to remove the manual loop unrolling in __find_if for GCC
> 15, which should allow the compiler to optimize it better, potentially
> auto-vectorizing. That might make memchr less advantageous, but I think it's
> worth doing anyway.

This is great news!

  parent reply	other threads:[~2024-05-14 22:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 20:29 [Bug libstdc++/88545] New: " gcc at gms dot tf
2024-05-10 23:22 ` [Bug libstdc++/88545] " sjames at gcc dot gnu.org
2024-05-13 13:00 ` redi at gcc dot gnu.org
2024-05-13 14:18 ` redi at gcc dot gnu.org
2024-05-14 22:33 ` gcc at gms dot tf [this message]
2024-05-14 22:55 ` hiraditya at msn dot com
2024-05-14 22:57 ` hiraditya at msn dot com
2024-06-03 18:37 ` hiraditya at msn dot com
2024-06-05  9:16 ` redi at gcc dot gnu.org
2024-06-05 15:33 ` redi at gcc dot gnu.org

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=bug-88545-4-e1WYGsZZdL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).