public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109383] [QoI] std::type_index::operator<=> should not call __builtin_strcmp twice Date: Mon, 03 Apr 2023 10:05:31 +0000 [thread overview] Message-ID: <bug-109383-4-Od7ljQ091F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109383-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109383 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-04-03 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- I guess we've all just implemented exactly what the standard says, without thinking about optimizing it. It's a good idea though, thanks!
next prev parent reply other threads:[~2023-04-03 10:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-03 3:12 [Bug libstdc++/109383] New: " de34 at live dot cn 2023-04-03 10:05 ` redi at gcc dot gnu.org [this message] 2023-04-03 10:35 ` [Bug libstdc++/109383] " redi at gcc dot gnu.org 2023-04-03 10:37 ` redi at gcc dot gnu.org 2023-04-04 0:50 ` pinskia 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-109383-4-Od7ljQ091F@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: linkBe 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).