public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/11706] std::pow(T, int) implementation pessimizes code
Date: Tue, 29 Jul 2003 13:19:00 -0000 [thread overview]
Message-ID: <20030729131917.18570.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030729120327.11706.rguenth@tat.physik.uni-tuebingen.de>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11706
------- Additional Comments From gdr at integrable-solutions dot net 2003-07-29 13:19 -------
Subject: Re: std::pow(T, int) implementation pessimizes code
"steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| Or are there reasons bigger than us that prevent such an implementation from
| being correct?
The expansion of pow() as an inline function may be quite large and
have negative impact on the overall program. That is why it does not
suffice to examine the assembler output nor just a single (kind) of
application -- be it scientific.
This is not meant to dismiss the report. I'll take care of it.
-- Gaby
next prev parent reply other threads:[~2003-07-29 13:19 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 12:03 [Bug libstdc++/11706] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 12:39 ` [Bug libstdc++/11706] " steven at gcc dot gnu dot org
2003-07-29 12:53 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 13:01 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-07-29 13:19 ` gdr at integrable-solutions dot net [this message]
2003-08-23 1:56 ` dhazeghi at yahoo dot com
2003-09-29 15:05 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-09-29 15:11 ` gdr at integrable-solutions dot net
2003-09-29 15:29 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-09-29 15:41 ` gdr at integrable-solutions dot net
2003-09-29 15:43 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-09-29 17:30 ` Gabriel Dos Reis
2003-09-29 17:36 ` gdr at integrable-solutions dot net
2003-11-13 21:42 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-12-05 23:52 ` bkoz at gcc dot gnu dot org
2003-12-06 18:26 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-12-06 19:26 ` gdr at integrable-solutions dot net
2003-12-06 19:50 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-12-06 20:05 ` rguenth at tat dot physik dot uni-tuebingen dot de
2003-12-06 20:33 ` gdr at integrable-solutions dot net
2004-03-10 15:14 ` pcarlini at suse dot de
2004-03-10 15:34 ` gdr at integrable-solutions dot net
2004-03-10 15:43 ` pcarlini at suse dot de
2004-03-10 19:51 ` gdr at integrable-solutions dot net
2004-03-10 20:01 ` pcarlini at suse dot de
2004-03-10 20:19 ` gdr at integrable-solutions dot net
2004-03-10 20:26 ` pcarlini at suse dot de
2004-03-10 20:43 ` gdr at integrable-solutions dot net
2004-03-10 22:27 ` pcarlini at suse dot de
2004-03-10 22:39 ` gdr at integrable-solutions dot net
2004-03-10 22:45 ` bangerth at dealii dot org
2004-03-10 22:47 ` pcarlini at suse dot de
2004-03-10 23:39 ` gdr at integrable-solutions dot net
2004-03-11 10:42 ` cvs-commit at gcc dot gnu dot org
2004-03-11 11:37 ` cvs-commit at gcc dot gnu dot org
2004-03-11 12:06 ` pcarlini at suse dot de
2004-03-11 18:55 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-03-11 19:04 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-03-11 20:14 ` rguenth at tat dot physik dot uni-tuebingen dot de
2004-03-12 1:43 ` rakdver at gcc dot gnu dot org
2004-05-16 22:22 ` pinskia at gcc dot gnu dot org
2004-09-23 18:22 ` pinskia at gcc dot gnu dot org
2004-10-02 4:04 ` pinskia at gcc dot gnu dot org
2004-10-02 4:06 ` pinskia at gcc dot gnu dot org
2005-01-12 16:17 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-02-07 22:33 ` rguenth at gcc dot gnu dot org
2005-02-10 0:43 ` rguenth at gcc dot gnu dot org
2005-02-10 1:13 ` rguenth at gcc dot gnu dot org
2005-02-10 1:13 ` pcarlini at suse dot de
2005-02-13 19:18 ` pcarlini at suse dot de
2005-02-13 19:18 ` cvs-commit at gcc dot gnu dot org
2005-05-07 19:56 ` 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=20030729131917.18570.qmail@sources.redhat.com \
--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: link
Be 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).