public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8
Date: Fri, 27 Jul 2007 21:43:00 -0000	[thread overview]
Message-ID: <20070727214340.27551.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32841-12313@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2007-07-27 21:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 20:40 [Bug testsuite/32841] New: FAIL: gfortran.dg/edit_real_1.f90 on Darwin8 dominiq at lps dot ens dot fr
2007-07-20 20:54 ` [Bug testsuite/32841] " jvdelisle at gcc dot gnu dot org
2007-07-20 21:00 ` dominiq at lps dot ens dot fr
2007-07-20 21:01 ` jvdelisle at gcc dot gnu dot org
2007-07-20 21:20 ` dominiq at lps dot ens dot fr
2007-07-20 21:41 ` jvdelisle at gcc dot gnu dot org
2007-07-20 22:08 ` dominiq at lps dot ens dot fr
2007-07-20 22:21 ` jvdelisle at gcc dot gnu dot org
2007-07-20 22:28 ` dominiq at lps dot ens dot fr
2007-07-23 14:53 ` dominiq at lps dot ens dot fr
2007-07-23 15:03 ` dominiq at lps dot ens dot fr
2007-07-24  9:31 ` [Bug libfortran/32841] [4.3 regression libfortran] HUGE(1.0d0) is written a +Infinity " dominiq at lps dot ens dot fr
2007-07-25  4:45 ` [Bug libfortran/32841] [4.3 regression] " jvdelisle at gcc dot gnu dot org
2007-07-25  5:28 ` jvdelisle at gcc dot gnu dot org
2007-07-25  6:38 ` dominiq at lps dot ens dot fr
2007-07-25  6:41 ` dominiq at lps dot ens dot fr
2007-07-25 22:39 ` jvdelisle at gcc dot gnu dot org
2007-07-27  5:56 ` dominiq at lps dot ens dot fr
2007-07-27  6:50 ` [Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) output as +Infinity on ppc-darwin8 fxcoudert at gcc dot gnu dot org
2007-07-27 19:34 ` dominiq at lps dot ens dot fr
2007-07-27 20:41 ` jvdelisle at gcc dot gnu dot org
2007-07-27 21:43 ` dominiq at lps dot ens dot fr [this message]
2007-07-27 23:46 ` fxcoudert at gcc dot gnu dot org
2007-08-31  1:15 ` pinskia at gcc dot gnu dot org
2007-09-05  1:30 ` mmitchel at gcc dot gnu dot org
2007-09-29 23:15 ` [Bug libfortran/32841] [4.3 regression] HUGE(1.0_16) " fxcoudert at gcc dot gnu dot org
2007-09-29 23:20 ` fxcoudert at gcc dot gnu dot org
2008-01-17 11:25 ` [Bug libfortran/32841] [4.3 regression] HUGE(1.0_16) output as +Infinity on ppc-darwin8 (gfortran.dg/large_real_kind_2.F90) burnus at gcc dot gnu dot org
2008-01-25 15:46 ` dominiq at lps dot ens dot fr
2008-02-21 13:50 ` [Bug libfortran/32841] [4.3/4.4 " fxcoudert at gcc dot gnu dot org
2008-02-24 12:00 ` fxcoudert at gcc dot gnu dot org
2008-02-24 12:03 ` fxcoudert at gcc dot gnu dot org
2008-02-24 12:10 ` fxcoudert at gcc dot gnu dot org
2008-02-25 13:47 ` dominiq at lps dot ens dot fr
2008-03-12 10:36 ` fxcoudert at gcc dot gnu dot org

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=20070727214340.27551.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).