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++/113807] [performance] bitset::set not using memset opportunity Date: Thu, 15 Feb 2024 12:40:44 +0000 [thread overview] Message-ID: <bug-113807-4-JuT56criKZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113807-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113807 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |14.0 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- I'm surprised the compiler can't optimize _M_do_set() and operator== already, but it looks like it doesn't recognize the trivial loops.
next prev parent reply other threads:[~2024-02-15 12:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-07 12:34 [Bug libstdc++/113807] New: " rhalbersma at gmail dot com 2024-02-08 12:55 ` [Bug libstdc++/113807] " redi at gcc dot gnu.org 2024-02-15 11:44 ` cvs-commit at gcc dot gnu.org 2024-02-15 11:53 ` rhalbersma at gmail dot com 2024-02-15 12:40 ` redi at gcc dot gnu.org [this message] 2024-02-15 12:45 ` jakub at gcc dot gnu.org 2024-02-15 12:51 ` rguenth at gcc dot gnu.org 2024-02-15 13:10 ` redi at gcc dot gnu.org 2024-02-15 13:36 ` rhalbersma at gmail dot com 2024-02-15 13:43 ` redi at gcc dot gnu.org 2024-05-07 7:44 ` rguenth 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-113807-4-JuT56criKZ@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).