From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Bradley Lucier <lucier@math.purdue.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: why not consfold sin(const)
Date: Thu, 23 Sep 2004 23:04:00 -0000 [thread overview]
Message-ID: <41532DD7.4090405@moene.indiv.nluug.nl> (raw)
In-Reply-To: <80881DE8-0D0B-11D9-B25D-003065BA681E@math.purdue.edu>
Bradley Lucier wrote:
>> All functions in <math.h> can set errno for domain and range errors;
>> in other words, those functions are not pure, and cannot be moved out
>> of loops or CSE'd away.
>
> Which is one reason to have -fno-math-errno (which is part of -ffast-math).
Sure, but the original implementation of -fno-math-errno I coded because
Fortran programmers wouldn't have access to errno anyway, didn't concern
itself with the pureness (or even constness) of the resulting <math.h>
function.
This is a later addition.
--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Maintainer, GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
A maintainer of GNU Fortran 95: http://gcc.gnu.org/fortran/
next prev parent reply other threads:[~2004-09-23 20:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 11:35 Bradley Lucier
2004-09-23 23:04 ` Toon Moene [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-19 16:02 Luchezar Belev
2004-09-19 18:00 ` Robert Dewar
2004-09-19 19:17 ` Luchezar Belev
2004-09-19 19:31 ` Robert Dewar
2004-09-19 19:55 ` Luchezar Belev
2004-09-19 20:25 ` Robert Dewar
2004-09-19 20:34 ` Luchezar Belev
2004-09-19 20:56 ` Zack Weinberg
2004-09-20 8:15 ` Kai Henningsen
2004-09-19 21:12 ` Robert Dewar
2004-09-19 20:53 ` Timothy J.Wood
2004-09-19 22:41 ` Robert Dewar
2004-09-20 0:31 ` Timothy J.Wood
2004-09-20 4:27 ` Robert Dewar
2004-09-20 5:44 ` Dale Johannesen
2004-09-20 19:43 ` Toon Moene
2004-09-20 20:34 ` Kaveh R. Ghazi
2004-09-20 23:31 ` Robert Dewar
2004-09-21 0:13 ` Scott Robert Ladd
2004-09-21 5:18 ` Steven Bosscher
2004-09-21 5:55 ` Scott Robert Ladd
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=41532DD7.4090405@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=gcc@gcc.gnu.org \
--cc=lucier@math.purdue.edu \
/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).