public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François-Xavier Coudert" <fxcoudert@gmail.com>
To: gfortran <fortran@gcc.gnu.org>, GCC Development <gcc@gcc.gnu.org>
Subject: gfortran and -mlong-double-128
Date: Thu, 16 Feb 2006 11:09:00 -0000	[thread overview]
Message-ID: <19c433eb0602160309y754cf258kd00227b6d80bff2b@mail.gmail.com> (raw)

Hi all,

I'm sending this mail because I'm a bit confused about the
-mlong-double-128 option on (for example) ppc64-linux, and its impact
on gfortran/libgfortran.

When I simply bootstrap a compiler with "configure
--with-cpu=default32", I get a gfortran that does only have kind=4 and
kind=8 reals (corresponding to C types float and double) by default.
When I use this gfortran with the -mlong-double-128 option, the
real(kind=16) floating point type is accepted at compile-time, but the
I/O library in libgfortran doesn't know how to deal with it (since,
when libgfortran was compiled, it did not detect that real(kind=16)
was available), and the code fails at runtime.

What should we do about that? I see a few options:
  1. refuse -mlong-double-128 for Fortran code; easiest, but not
exactly satisfying
  2. build multiple instances of the library, as is currently done for
the -m32/-m64 options
  3. build only one instance of the library, but build it with
-mlong-double-128 enabled, since as far as libgfortran is concerned,
it only adds a new floating-point type.

I may be confused about how all this is supposed to be handled, so any
pointer to further reading is welcome, as well as opinion on the
problem and options above.

Thanks,
FX

             reply	other threads:[~2006-02-16 11:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 11:09 François-Xavier Coudert [this message]
2006-02-16 12:50 ` Richard Guenther
2006-02-16 12:57   ` François-Xavier Coudert
2006-02-16 14:11     ` Jakub Jelinek
2006-02-16 15:17       ` Richard Guenther
2006-02-16 15:04 ` Paul Brook
2006-02-16 15:14   ` François-Xavier Coudert
2006-02-16 15:17     ` Paul Brook
2006-02-16 15:19   ` Richard Guenther
2006-02-16 15:24     ` Andrew Pinski
2006-02-16 15:28     ` Paul Brook
2006-02-16 15:48       ` Jakub Jelinek

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=19c433eb0602160309y754cf258kd00227b6d80bff2b@mail.gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@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).