From: FX <fxcoudert@gmail.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>
Cc: Bernd Schmidt <bschmidt@redhat.com>,
Janne Blomqvist <jb@gcc.gnu.org>, Tobias Burnus <burnus@net-b.de>,
FranC'ois-Xavier Coudert <fxcoudert@gcc.gnu.org>,
Jerry DeLisle <jvdelisle@gcc.gnu.org>,
Erik Edelmann <erik.edelmann@iki.fi>,
Daniel Franke <franke.daniel@gmail.com>,
Thomas KC6nig <tkoenig@gcc.gnu.org>, Daniel Kraft <d@domob.eu>,
Toon Moene <toon@moene.org>, Mikael Morin <mikael.morin@sfr.fr>,
tobias.schlueter@physik.uni-muenchen.de,
Paul Thomas <pault@gcc.gnu.org>, Janus Weil <janus@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH #3], Fix _Complex when there are multiple FP types the same size
Date: Mon, 02 May 2016 21:24:00 -0000 [thread overview]
Message-ID: <84EB8F4B-103C-4534-904E-A2A7CA067A7F@gmail.com> (raw)
In-Reply-To: <20160502211024.GA17046@ibm-tiger.the-meissners.org>
Hi Michael,
Thanks for letting us know.
Right now, the Fortran front-end uses the following real modes:
- those corresponding to {float,double,long_double}_type_node
- TFmode (if libquadmath support is enabled)
and then uses the corresponding complex modes.
So, I guess the question in your case is: in each compiler settings, is there a TFmode? If so, that would not play nice: the front-end current does not handle several real modes with equal precision.
In case you want to test, simple Fortran code to create a 128-bit real x and complex y is:
real(kind=16) :: x
complex(kind=16) :: y
I’m guessing if that emits the correct code in both settings, the rest should be fine.
--
FX
next prev parent reply other threads:[~2016-05-02 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 21:06 [PATCH], " Michael Meissner
2016-04-28 22:10 ` Segher Boessenkool
2016-04-28 23:41 ` Michael Meissner
2016-04-29 20:51 ` [PATCH #2], " Michael Meissner
2016-04-30 16:00 ` Segher Boessenkool
2016-05-02 10:54 ` Bernd Schmidt
2016-05-02 21:10 ` [PATCH #3], " Michael Meissner
2016-05-02 21:24 ` FX [this message]
2016-05-02 21:47 ` Michael Meissner
2016-05-02 22:30 ` Michael Meissner
2016-05-02 23:06 ` Bernd Schmidt
2016-05-05 13:36 ` 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=84EB8F4B-103C-4534-904E-A2A7CA067A7F@gmail.com \
--to=fxcoudert@gmail.com \
--cc=bschmidt@redhat.com \
--cc=burnus@net-b.de \
--cc=d@domob.eu \
--cc=dje.gcc@gmail.com \
--cc=erik.edelmann@iki.fi \
--cc=franke.daniel@gmail.com \
--cc=fxcoudert@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=jb@gcc.gnu.org \
--cc=jvdelisle@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
--cc=mikael.morin@sfr.fr \
--cc=pault@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tkoenig@gcc.gnu.org \
--cc=tobias.schlueter@physik.uni-muenchen.de \
--cc=toon@moene.org \
--cc=wschmidt@linux.vnet.ibm.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).