public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "R. D. Flowers" <rd@chatta.us>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Robert Dewar <dewar@gnat.com>,
	Zack Weinberg <zack@codesourcery.com>,
	 gcc@gcc.gnu.org
Subject: Re: jFP religious wars
Date: Mon, 22 Mar 2004 12:45:00 -0000	[thread overview]
Message-ID: <405E6708.70508@chatta.us> (raw)
In-Reply-To: <m33c815zts.fsf@uniton.integrable-solutions.net>

Gabriel Dos Reis wrote:

> Robert Dewar <dewar@gnat.com> writes:
> 
> | Zack Weinberg wrote:
> | > "R. D. Flowers" <rd@chatta.us> writes:
> | >
> | >>would not some flag like -fp-pedantic (or however to fit in the
> | >>namespace) be a good idea (for both decent sets of folks: the
> | >>fast-and-a-little-dirty and the clean-and-a-little-slow people)?
> | > Maybe.  What would it do?
> | 
> | I don't think this would work. There is nothing "pedantic" in
> | the carefully formulated rules that make it easier/possible
> | to write accurate floating-point code. It is far better to
> | have the existing flags for -ffast-math etc, which clearly
> | warn that the resulting semantics may be unreliable.
> 
> Fully agreed.
> 
> | The use of -pedantic to cover little used language features
> | or rules is one thing, the use of a flag like this to give
> | incorrect semantics.


Welllll, as far as what to do, you folks probably do in fact know best.

But, if some code is broken by -pedantic, isn't it also incorrect in SOME picky litte sense? 

That people in some of their actual situations might not care about? Similar (in some actual situations) to not caring about that final shred of accuracy?


> 
> In fact, the flag "-pedantic" is misnamed -- at least, for what it does
> currently in C++ (I think the same is true for C).  It is there only
> for historical accident.  Multiplying that naming by a factor greater
> than 1 would be misguided.
> 
> -- Gaby
> 
> 
> 


-- 

R. D. Flowers, O. H.
Xinna R. Coloohiy
The Bear At Home
Now a single dad.

I   M i s s   A m e r i c a

http://chalice.us/mylinks
http://chalice.us/pho
http://chalice.us/poe
http://chatta.us/resume.txt
Mailing lists at http://chatta.us

-- "He who cannot protect himself or his nearest and dearest or
their honor by non-violently facing death may and ought to do so
by violently dealing with the oppressor. He who can do neither of
the two is a burden."
-- Mohandes Ghandi

Refer !
Stop Tritium !

  reply	other threads:[~2004-03-22  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1079845736.15963.ezmlm@gcc.gnu.org>
2004-03-22  2:08 ` gcc Digest 21 Mar 2004 05:08:56 -0000 Issue 3435 R. D. Flowers
2004-03-22  2:39 ` jFP religious wars R. D. Flowers
2004-03-22  3:35   ` Zack Weinberg
2004-03-22  4:00     ` R. D. Flowers
2004-03-22  8:06       ` Robert Dewar
2004-03-22  8:03     ` Robert Dewar
2004-03-22 11:37       ` Gabriel Dos Reis
2004-03-22 12:45         ` R. D. Flowers [this message]
2004-03-22 13:25           ` Robert Dewar

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=405E6708.70508@chatta.us \
    --to=rd@chatta.us \
    --cc=base@chatta.us \
    --cc=dewar@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=zack@codesourcery.com \
    /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).