> Well, you're going to have to ask a numerical analyst about this. If you
> take that stance then -ffast-math is always wrong, no matter what the
> combination of other switches. The "wrong" results might be harder to
> reproduce without any optimization going on, but they could still happen.
Thomas Lockhart writes:
> ?? I think we agree. It happens to be the case that slightly incorrect
> results are wrong results, and that full IEEE math conformance gives
> exactly correct results. For the case of date/time, the "slightly wrong"
> results round up to 60.0 seconds for times on an eve
> You're reading this wrong. What this means is:
> "If you're working on GCC, do not ever think of enabling -ffast-math
> implicitly by any -Ox level [since most other -fxxx options are grouped
> under some -Ox], since programs that might want optimization could still
> depend on correct IEEE mat
Justin Clift <[EMAIL PROTECTED]> writes:
>> So, I'm still looking for the best way to add a compile flag while
>> making it clear that it is for one distro only.
Since this is only an RPM problem, it should be solved in the RPM spec
file, not by hacking the configure script. We had at least one
Justin Clift <[EMAIL PROTECTED]> writes:
> It's not "Mandrake" that will be broken. Mandrake is also often used by
> new Linux users who wouldn't have the slightest idea about setting GCC
> options. It'll be THEM that have broken installations if we take this
> approach (as an aside, that means
Is the right approach for the ./configure script to check for the
existence of the /etc/mandrake-release file as at least an initial
indicator that the compile is happening on Mandrake?
Regards and best wishes,
Justin Clift
Thomas Lockhart wrote:
>
> > If Mandrake wants to be broken, let them
NO!
It's not "Mandrake" that will be broken. Mandrake is also often used by
new Linux users who wouldn't have the slightest idea about setting GCC
options. It'll be THEM that have broken installations if we take this
approach (as an aside, that means that WE will be probably also be
answering m
Thomas Lockhart writes:
> Mandrake (as of 7.2) still does a brain-dead mix of "-O3" and
> "-ffast-math", which is a risky and unnecessary combination according to
> the gcc folks (and which kills some of our date/time rounding). From the
> man page for gcc:
>
> -ffast-math
> This option should
> If Mandrake wants to be broken, let them - and tell them.
They know ;) But just as with RH, they build ~1500 packages, so it is
probably not realistic to get them to change their build standards over
one misbehavior in one package.
The goal here is to get PostgreSQL to work well for as many pl
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> > It's a good start to test with for the purposes for which I think you want to
> > test for. (and I'm an English teacher by night -- argh).
>
> :)
>
> Mandrake (as of 7.2) still does a brain-dead mix of "-O3" and
> "-ffast-math", which is a risky
> It's a good start to test with for the purposes for which I think you want to
> test for. (and I'm an English teacher by night -- argh).
:)
Mandrake (as of 7.2) still does a brain-dead mix of "-O3" and
"-ffast-math", which is a risky and unnecessary combination according to
the gcc folks (and
11 matches
Mail list logo
