public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "scc at teamt5 dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66414] string::find ten times slower than strstr
Date: Mon, 11 Sep 2023 17:03:38 +0000	[thread overview]
Message-ID: <bug-66414-4-9vYrmDcu2y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66414-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Chih-Hsuan Yang <scc at teamt5 dot org> ---
Hi all,


I hope this message finds you well.

I wanted to inquire about the current status of our project. It has come to my
attention that our program is facing performance issues when using gcc 13.2.
Considering this situation, I am willing to take on the responsibility of
addressing this issue by taking ownership of the related ticket.

Could you please provide an update on the progress here?

Thank you for your attention to this matter.

  parent reply	other threads:[~2023-09-11 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  7:59 [Bug libstdc++/66414] New: Regression: " neleai at seznam dot cz
2020-03-24 17:24 ` [Bug libstdc++/66414] " hiraditya at msn dot com
2021-01-27 13:34 ` redi at gcc dot gnu.org
2021-01-27 13:47 ` cvs-commit at gcc dot gnu.org
2023-09-11 17:03 ` scc at teamt5 dot org
2023-09-11 17:03 ` scc at teamt5 dot org [this message]
2023-09-11 17:04 ` scc at teamt5 dot org
2023-09-11 17:22 ` scc at teamt5 dot org
2023-09-11 19:09 ` redi at gcc dot gnu.org
2023-09-12  2:55 ` scc at teamt5 dot org
2023-09-12  7:31 ` 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-66414-4-9vYrmDcu2y@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).