From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Janus Weil <janus@gcc.gnu.org>
Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>,
David Edelsohn <dje.gcc@gmail.com>,
Janne Blomqvist <blomqvist.janne@gmail.com>,
Fortran List <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 82143: add a -fdefault-real-16 flag
Date: Tue, 26 Sep 2017 09:12:00 -0000 [thread overview]
Message-ID: <yddlgl1x1r4.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CAKwh3qhkWVV-DzyN1JQPhse=Q9ZZSQaDReGoHi5=drgLMLBY+Q@mail.gmail.com> (Janus Weil's message of "Tue, 26 Sep 2017 11:03:12 +0200")
Hi Janus,
> Attached is a more complete patch, which should fix all problems that
> were reported concerning these two test cases. Would be great if
> someone could confirm that it works on a failing target (I currently
> only have access to x86_64-linux-gnu machines).
I've just checked sparc-sun-solaris2.11: works fine. promotion_3.f90
PASSes as before, but promotion_4.f90 is now UNSUPPORTED instead of
failing.
> Ok for trunk?
The new fortran_real_10 effective-target keyword needs documenting in
sourcebuild.texi.
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2017-09-26 9:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:07 David Edelsohn
2017-09-25 21:14 ` Janus Weil
2017-09-25 21:23 ` Steve Kargl
2017-09-26 8:44 ` Janus Weil
2017-09-26 9:03 ` Janus Weil
2017-09-26 9:12 ` Rainer Orth [this message]
2017-09-26 9:47 ` Janus Weil
2017-09-26 14:54 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 9:38 Dominique d'Humières
2017-09-18 9:31 Dominique d'Humières
2017-09-18 18:13 ` Janus Weil
2017-09-22 10:06 ` Dominique d'Humières
2017-09-22 11:21 ` Janus Weil
2017-09-22 14:37 ` Steve Kargl
2017-09-22 22:46 ` Dominique d'Humières
2017-09-22 23:47 ` Steve Kargl
2017-12-03 17:36 ` Gerald Pfeifer
2017-09-17 20:42 Janus Weil
2017-09-18 4:51 ` Steve Kargl
2017-09-18 7:02 ` Janus Weil
2017-09-18 14:08 ` Steve Kargl
2017-09-18 17:57 ` Janus Weil
2017-09-21 7:10 ` Janus Weil
2017-09-21 20:38 ` Steve Kargl
2017-09-22 5:03 ` Janus Weil
2017-09-22 7:12 ` Janne Blomqvist
2017-09-22 9:44 ` Janus Weil
2017-09-22 19:32 ` Janus Weil
2017-09-23 13:19 ` Janus Weil
2017-09-22 14:06 ` Steve Kargl
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=yddlgl1x1r4.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=blomqvist.janne@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janus@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).