public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/40106] [4.4/4.5 Regression] Weird interaction between optimize_insn_for_speed_p and -funsafe-math-optimizations
Date: Tue, 16 Mar 2010 16:04:00 -0000	[thread overview]
Message-ID: <20100316160426.16164.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40106-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #41 from dominiq at lps dot ens dot fr  2010-03-16 16:04 -------
> > > Especially on embedded targets with soft-float the multiplication would
> > > add a significant code size penalty.
> > 
> > Even in this case this would strongly of the code. It may be true if other
> > pieces require log and exp. If not I seriously doubt that replacing the code
> > for multiplies and square roots will be larger than the code for log and exp.
> 
> Parse error.

Sorry, is "stongly depend on the code" and  "If not, I seriously doubt that
replacing the code for multiplies and square roots will be larger than the code
for log and exp." better? 

pow(a,b) == exp(b*log(a)), so if 'a' is not a constant, you need the code for
log and exp to evaluate x*sqrt(x) as pow(x,1.5), instead of the code for
multiply and sqrt (note that I cannot see how the code for log and exp could
not require the code for multiply). If log or exp codes are not needed by other
parts of the whole program, x*sqrt(x) will almost certainly gives a more
compact code than pow(x,1.5).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40106


  parent reply	other threads:[~2010-03-16 16:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 18:04 [Bug middle-end/40106] New: Time increase with inlining for the Polyhedron test air.f90 dominiq at lps dot ens dot fr
2009-05-12 11:52 ` [Bug middle-end/40106] " hubicka at gcc dot gnu dot org
2009-05-12 13:23 ` dominiq at lps dot ens dot fr
2009-05-12 14:47 ` rguenther at suse dot de
2009-05-12 16:18 ` dominiq at lps dot ens dot fr
2009-05-22 20:39 ` dominiq at lps dot ens dot fr
2009-05-22 20:41 ` dominiq at lps dot ens dot fr
2009-05-22 20:52 ` dominiq at lps dot ens dot fr
2009-07-13 15:29 ` burnus at gcc dot gnu dot org
2009-08-25 11:56 ` dominiq at lps dot ens dot fr
2009-08-25 12:01 ` [Bug middle-end/40106] Time increase " dominiq at lps dot ens dot fr
2009-08-25 12:22 ` [Bug middle-end/40106] Time increase with inlining " rguenth at gcc dot gnu dot org
2009-08-25 12:30 ` dominiq at lps dot ens dot fr
2009-08-25 12:40 ` rguenther at suse dot de
2009-08-25 12:51 ` dominiq at lps dot ens dot fr
2009-08-25 15:31 ` dominiq at lps dot ens dot fr
2009-08-25 21:25 ` [Bug middle-end/40106] Time increase for the Polyhedron test air.f90 due to bad optimization dominiq at lps dot ens dot fr
2009-08-27 21:59 ` dominiq at lps dot ens dot fr
2009-08-28  1:09 ` howarth at nitro dot med dot uc dot edu
2009-08-28  5:39 ` dominiq at lps dot ens dot fr
2009-08-28  7:19 ` dominiq at lps dot ens dot fr
2009-08-28 12:01 ` dominiq at lps dot ens dot fr
2009-08-28 12:23 ` dominiq at lps dot ens dot fr
2009-08-28 13:36 ` howarth at nitro dot med dot uc dot edu
2009-08-31 13:06 ` dominiq at lps dot ens dot fr
2009-08-31 15:04 ` dominiq at lps dot ens dot fr
2009-08-31 15:21 ` jv244 at cam dot ac dot uk
2009-08-31 15:23 ` rguenther at suse dot de
2009-08-31 23:59 ` dominiq at lps dot ens dot fr
2009-09-01  9:37 ` dominiq at lps dot ens dot fr
2009-09-03  7:10 ` [Bug middle-end/40106] [4.4/4.5 Regression] " dominiq at lps dot ens dot fr
2009-09-03 11:20 ` dominiq at lps dot ens dot fr
2009-09-06 22:15 ` rguenth at gcc dot gnu dot org
2009-09-18  8:58 ` rguenth at gcc dot gnu dot org
2009-10-15 12:49 ` jakub at gcc dot gnu dot org
2009-10-18 13:22 ` rguenth at gcc dot gnu dot org
2009-12-15 16:40 ` rguenth at gcc dot gnu dot org
2010-01-21 13:16 ` jakub at gcc dot gnu dot org
2010-02-25 17:20 ` [Bug middle-end/40106] [4.4/4.5 Regression] Weird interaction between optimize_insn_for_speed_p and -funsafe-math-optimizations dominiq at lps dot ens dot fr
2010-03-16 15:07 ` dominiq at lps dot ens dot fr
2010-03-16 15:11 ` rguenther at suse dot de
2010-03-16 15:26 ` rguenth at gcc dot gnu dot org
2010-03-16 15:50 ` dominiq at lps dot ens dot fr
2010-03-16 15:52 ` rguenther at suse dot de
2010-03-16 16:04 ` dominiq at lps dot ens dot fr [this message]
2010-03-16 16:07 ` rguenther at suse dot de
2010-03-16 16:39 ` dominiq at lps dot ens dot fr
2010-03-16 16:59 ` jakub at gcc dot gnu dot org
2010-03-16 17:14 ` dominiq at lps dot ens dot fr
2010-03-18 18:30 ` dominiq at lps dot ens dot fr
2010-03-19 10:26 ` rguenth at gcc dot gnu dot org
2010-03-19 10:35 ` rguenth at gcc dot gnu dot org
2010-03-19 15:40 ` dominiq at lps dot ens dot fr
2010-03-20 13:03 ` dominiq at lps dot ens dot fr
2010-03-20 13:21 ` dominiq at lps dot ens dot fr
2010-03-20 14:19 ` rguenther at suse dot de
2010-03-20 14:40 ` dominiq at lps dot ens dot fr
2010-03-20 15:00 ` rguenth at gcc dot gnu dot org
2010-03-20 15:12 ` rguenth at gcc dot gnu dot org
2010-03-22 10:36 ` rguenth at gcc dot gnu dot org
2010-03-22 12:38 ` rguenth at gcc dot gnu dot org
2010-03-22 12:39 ` [Bug middle-end/40106] [4.4 " rguenth at gcc dot gnu dot org
2010-03-25 17:38 ` hubicka at gcc dot gnu dot org
2010-04-30  9:01 ` jakub 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=20100316160426.16164.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).