public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/30204] std::vector operator[] 10x speedup (patch) Date: Thu, 14 Dec 2006 11:20:00 -0000 [thread overview] Message-ID: <20061214111824.22925.qmail@sourceware.org> (raw) In-Reply-To: <bug-30204-13750@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from pcarlini at suse dot de 2006-12-14 11:18 ------- By the way, forgot that in mainline and 4.2 branch the issue simply doesn't exist anymore: for completely different reasons, we are *already* using directly _M_start, _M_finish, and co. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30204
next prev parent reply other threads:[~2006-12-14 11:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-13 18:01 [Bug libstdc++/30204] New: " charles at rebelbase dot com 2006-12-13 18:09 ` [Bug libstdc++/30204] " chris at bubblescope dot net 2006-12-14 2:50 ` pinskia at gcc dot gnu dot org 2006-12-14 10:34 ` pcarlini at suse dot de 2006-12-14 11:20 ` pcarlini at suse dot de [this message] 2006-12-14 17:58 ` charles at rebelbase dot com
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=20061214111824.22925.qmail@sourceware.org \ --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).