public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/102015] [missed optimization] Small memory overhead in _Rb_tree_impl (fix would require ABI break) Date: Sun, 22 Aug 2021 19:17:10 +0000 [thread overview] Message-ID: <bug-102015-4-5jr5QJGsCt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102015-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102015 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- https://stackoverflow.com/questions/66573773/is-there-a-reason-for-8-bytes-of-size-overhead-in-libstdc-stdmultiset-map
next prev parent reply other threads:[~2021-08-22 19:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-22 17:36 [Bug c++/102015] New: " kamkaz at windowslive dot com 2021-08-22 19:17 ` pinskia at gcc dot gnu.org [this message] 2021-08-22 21:08 ` [Bug libstdc++/102015] " kamkaz at windowslive dot com 2021-08-23 9:45 ` redi at gcc dot gnu.org 2021-08-31 18:27 ` redi at gcc dot gnu.org 2021-08-31 18:28 ` 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-102015-4-5jr5QJGsCt@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).