This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8



------- Comment #21 from dominiq at lps dot ens dot fr  2007-07-27 21:43 -------
Subject: Re:  [4.3 regression] HUGE(1.0d0) output as
 +Infinity on ppc-darwin8

> Your idea on the order of #defines is probably on the right track.

As I said, this is the quickest way to hide the problem.
I have tested that it works and it's only the matter
to know the equivalent of __CYGWIN__ for powerpc-darwin to
implement it.

Indeed it won't help to understand the origin of the problem
which may resurface in an other context. It would help
to have answers to the following questions:

(1) why isfinite(DBL_MAX) is working, but not isfinite(HUGE(1.0d0))?
Does libfortran convert HUGE(1.0d0) to long double?
If not, what's happening?

(2) Does configure use the system gcc or xgcc from the latest stage?
In the first case, this explain why HAVE_BROKEN_ISFINITE is not
defined, but raise the question of the relevance of building
gcc through 3 stages while keeping the config at stage 1.
I the second case, why HAVE_BROKEN_ISFINITE is not defined?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]