public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sylvain dot pion at sophia dot inria dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/6588] throw() takes 20,000 cycles : is it expected ? Date: Thu, 09 Apr 2009 10:06:00 -0000 [thread overview] Message-ID: <20090409100605.10557.qmail@sourceware.org> (raw) In-Reply-To: <bug-6588-1902@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from sylvain dot pion at sophia dot inria dot fr 2009-04-09 10:06 ------- There seems to have been some progress : it now takes 6000-9000 cycles instead of 20000. This is 6000 with g++ 4.3.1 on a Fedora 10 x86_64 box, and 9000 on a MacBook Pro with various g++ versions up to current mainline. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6588
next prev parent reply other threads:[~2009-04-09 10:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-6588-1902@http.gcc.gnu.org/bugzilla/> 2009-04-08 23:10 ` bangerth at gmail dot com 2009-04-09 10:06 ` sylvain dot pion at sophia dot inria dot fr [this message] [not found] <20020506163600.6588.sylvain.pion@sophia.inria.fr> 2005-01-13 21:23 ` pinskia at gcc dot gnu dot 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=20090409100605.10557.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).