Summary: | wrong double comparison result if taken from function result. | ||
---|---|---|---|
Product: | gcc | Reporter: | Richard Cognot <cognot> |
Component: | target | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | minor | CC: | gcc-bugs |
Priority: | P2 | ||
Version: | 3.4.2 | ||
Target Milestone: | --- | ||
Host: | Target: | i?86-*-* | |
Build: | Known to work: | ||
Known to fail: | Last reconfirmed: |
Description
Richard Cognot
2005-01-28 18:45:32 UTC
This is a dup of bug 323. The problem is excessive precission. *** This bug has been marked as a duplicate of 323 *** (In reply to comment #1) > This is a dup of bug 323. The problem is excessive precission. > > *** This bug has been marked as a duplicate of 323 *** Hi, Looking at the thread for bug #323 it would seem to happen only if optimization is turned on. in my case the bug is there even with -g2 -O0 -ffloat-store added to the compile line. Regards, Richard. Only happens on x86. (In reply to comment #3) > Only happens on x86. True. But only with gcc. Under Windows M$ .NET and DevStudio 6 give a correct result if "Improve float consitency" is turned on. Haven't tried with the Intel compiler yet. Will do from home. Regards, Richard. |