public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39280] Optimizing integer power
Date: Sun, 09 May 2010 21:09:00 -0000 [thread overview]
Message-ID: <20100509210856.1089.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39280-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from dfranke at gcc dot gnu dot org 2010-05-09 21:08 -------
Situation still the same with gcc version 4.6.0 20100509 (experimental) (GCC).
(In reply to comment #1)
> ... this asks for a POW_EXPR middle-end tree I guess. Or you can use
> builtins.c:expand_powi* do generate an expanded power series.
Would that be enough of a gain to be worth the effort?
--
dfranke at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dfranke at gcc dot gnu dot
| |org
OtherBugsDependingO| |36854
nThis| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39280
next prev parent reply other threads:[~2010-05-09 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 19:50 [Bug fortran/39280] New: " tkoenig at gcc dot gnu dot org
2009-02-24 10:10 ` [Bug fortran/39280] " rguenth at gcc dot gnu dot org
2009-02-24 12:01 ` burnus at gcc dot gnu dot org
2009-02-24 12:14 ` rguenther at suse dot de
2009-03-28 14:12 ` fxcoudert at gcc dot gnu dot org
2010-05-09 21:09 ` dfranke at gcc dot gnu dot org [this message]
2010-05-09 21:29 ` dominiq at lps dot ens dot fr
2010-05-10 8:41 ` rguenther at suse dot de
[not found] <bug-39280-4@http.gcc.gnu.org/bugzilla/>
2013-08-09 9:18 ` tkoenig 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=20100509210856.1089.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: 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).