From: Paul Brook <paul@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org, "François-Xavier Coudert" <fxcoudert@gmail.com>,
gfortran <fortran@gcc.gnu.org>
Subject: Re: gfortran and -mlong-double-128
Date: Thu, 16 Feb 2006 15:28:00 -0000 [thread overview]
Message-ID: <200602161528.47322.paul@codesourcery.com> (raw)
In-Reply-To: <84fc9c000602160718y4f4cd8c0v574924cc9ff2ea45@mail.gmail.com>
On Thursday 16 February 2006 15:18, Richard Guenther wrote:
> On 2/16/06, Paul Brook <paul@codesourcery.com> wrote:
> > On Thursday 16 February 2006 11:09, François-Xavier Coudert wrote:
> > > 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.
> >
> > Having gfortran magically know about certain ABI breaking options, and
> > doing funny things on certain targets seems a very bad precedent to me.
>
> The point is that from a gfortran perspective -mlong-double-128 doesn't
> change the ABI, it merely adds to it (which is sort of a change, but less
> invasive than changing long double from 8bytes to 16bytes). So we can
> easily cope with the user request for -mlong-double-128 by always providing
> the kind=16 intrinsics.
Except it [potentially] also changes the ABI that libgfortran uses to talk to
glibc. ie. a -mlong-double-128 libgfortran probably won't work with a
-mlong-double-64 glibc.
Paul
next prev parent reply other threads:[~2006-02-16 15:28 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
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 [this message]
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=200602161528.47322.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--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).