octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.0.1 release?


From: John W. Eaton
Subject: Re: 3.0.1 release?
Date: Tue, 08 Apr 2008 15:28:51 -0400

On  8-Apr-2008, David Bateman wrote:

| Yes this is the issue... It seems the bitmax under windows if not
| returning the right value.. bitmax uses
| 
| static_cast<double> (0x1FFFFFFFFFFFFFLL)
| 
| as its definition and so perhaps its the "LL" at the end that is causing
| the issue as it really should be a "UL".. Can you try
| 
| #include <iostream>
| int main (void)
| {
|         uint64_t a = 0x001FFFFFFFFFFFFFUL^0x0007FFFFFFFFFFFFUL;
|     double b = static_cast<double> (0x1FFFFFFFFFFFFFLL);
|     double c = static_cast<double> (0x1FFFFFFFFFFFFFUL);
|     std::cerr << 0x001FFFFFFFFFFFFFUL << std::endl;
|     std::cerr << 0x0007FFFFFFFFFFFFUL << std::endl;
|         std::cerr << a  << std::endl;
|         std::cerr << b  << std::endl;
|         std::cerr << c  << std::endl;
|         std::cerr << b - c  << std::endl;
|         return 0;
| }
| 
| and see whether the last result is something other than zero.. If so I
| think we've found the issue.

Do you think we can resolve this issue soon, or should I release 3.0.1
without a fix for the problem?

jwe


reply via email to

[Prev in Thread] Current Thread [Next in Thread]