public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/43554] profile-mode version of forward_list missing Date: Sun, 03 Oct 2010 09:22:00 -0000 [thread overview] Message-ID: <20101003092200.Y7GCzkVigAS9U30cWc_6O9_KQCNVzCqYHNLu3mBRxdc@z> (raw) In-Reply-To: <bug-43554-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43554 --- Comment #9 from Paolo Carlini <paolo.carlini at oracle dot com> 2010-10-03 09:22:41 UTC --- (In reply to comment #8) > What is the time frame for 4.6.0? We are still in Stage 1, but I don't have many details at the moment, I would suggest simply following the various announcements on the gcc mailing list. > For reference, what needs to be done at this point is a couple of new > diagnostics > 1. "forward_list to vector": if the only operations are "insert_after last > element" and iteration, and if the size is always about the same. > 2. "forward_list to deque": this needs a cost model. Ok... > Paolo, would it make sense to open tickets for other diagnostics as well, > even if it would take me a while to close them? Maybe some student out > there will pick them if they're well defined. If you ask me, normally we don't open many PRs for pure enhancement issues, the situation can quickly grow without control. After all, Bugzilla is for *bugs*. Thus I would recommend summarizing those issues to a minimal number of PRs, better if each has a student already "assigned", somehow.
next prev parent reply other threads:[~2010-10-03 9:22 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-43554-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 14:33 ` paolo.carlini at oracle dot com 2010-10-03 7:06 ` rus at google dot com 2010-10-03 7:40 ` rus at google dot com 2010-10-03 9:22 ` paolo.carlini at oracle dot com [this message] 2010-10-11 23:15 ` paolo.carlini at oracle dot com 2010-10-17 10:23 ` paolo.carlini at oracle dot com 2010-10-17 14:49 ` paolo at gcc dot gnu.org 2012-09-24 10:30 ` paolo.carlini at oracle dot com 2010-03-28 10:36 [Bug libstdc++/43554] New: " paolo dot carlini at oracle dot com 2010-03-28 10:36 ` [Bug libstdc++/43554] " paolo dot carlini at oracle dot com 2010-03-28 22:58 ` rus at google dot com 2010-03-29 0:10 ` paolo dot carlini at oracle dot com 2010-05-03 22:46 ` rus at google dot com 2010-05-03 23:06 ` paolo dot carlini at oracle dot com 2010-05-03 23:07 ` paolo dot carlini at oracle dot com 2010-05-03 23:13 ` rus at google dot com 2010-05-03 23:16 ` paolo dot carlini at oracle 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=20101003092200.Y7GCzkVigAS9U30cWc_6O9_KQCNVzCqYHNLu3mBRxdc@z \ --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).