public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "François-Xavier Coudert" <fxcoudert@gmail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: gfortran and -mlong-double-128
Date: Thu, 16 Feb 2006 12:57:00 -0000	[thread overview]
Message-ID: <19c433eb0602160457u3e82a90cme7ca7c60e18c0083@mail.gmail.com> (raw)
In-Reply-To: <84fc9c000602160450i10b7370aqcec3d373feb1cb64@mail.gmail.com>

> I guess libgfortran has configury to figure out if kind=16 is available?

Yes.

> If so then libgfortran should be built with -mlong-double-128, as this
> should only add extra symbols that do not conflict with kind=4 and kind=8
> ones.

Hum, that has to be done early in the configury (before all
autodetection). Do you think it's better suited at the beginning of
libgfortran/configure.ac (a special test, to see if -mlong-double-128
is available, and if it is add it to CFLAGS), or should it be done in
an upper level (and here is the limit of my understanding of the build
mechanism)?

> Am I correct that for gfortran there is no such thing as long double
> == double for -mlong-double-64?

This is right. Fortran has a list of available floating-point modes,
and they are chosen by a unique numbering scheme (the number is called
a "kind").

FX

  reply	other threads:[~2006-02-16 12:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 11:09 François-Xavier Coudert
2006-02-16 12:50 ` Richard Guenther
2006-02-16 12:57   ` François-Xavier Coudert [this message]
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=19c433eb0602160457u3e82a90cme7ca7c60e18c0083@mail.gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).