public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: Janus Weil <janus@gcc.gnu.org>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR 82143: add a -fdefault-real-16 flag
Date: Fri, 22 Sep 2017 10:06:00 -0000	[thread overview]
Message-ID: <E4300358-3883-49B8-A0AD-1649F69621C6@lps.ens.fr> (raw)
In-Reply-To: <CAKwh3qi5tSjkm2GjMaNR+qnfqN=L1xTjLYVWqs9N+_=4k7KcgQ@mail.gmail.com>


> Le 18 sept. 2017 à 20:13, Janus Weil <janus@gcc.gnu.org> a écrit :
> 
> 2017-09-18 11:31 GMT+02:00 Dominique d'Humières <dominiq@lps.ens.fr>:
>> (1) real(16) is an order of magnitude slower than real(8) for the codes I have tested (a long time ago). So its real utility is quite low.
> 
> I am fully aware that performance with quad-precision is lower than
> with double precision. How much will certainly depend on the specifics
> of the code in question.

Indeed! The polyhedron test protein.f90 goes from 19s to 32s.

> The flag I'm proposing would help in evaluating this performance hit.

My memory did not serve me well, for floating point intensive calculations it is not one order of magnitude but two (the one order of magnitude was probably for IBM REAL(16), i.e., two RAL(8))

Results for the original test_fpu.f90

Test1 - Gauss 2000 (101x101) inverts  1.1 sec  Err= 0.000000000000104
Test2 - Crout 2000 (101x101) inverts  1.2 sec  Err= 0.000000000000289
Test3 - Crout  2 (1001x1001) inverts  1.0 sec  Err= 0.000000000000082
Test4 - Lapack 2 (1001x1001) inverts  0.8 sec  Err= 0.000000000001333
                             total =  4.1 sec

Results for the REAL(10) variant

Test1 - Gauss 2000 (101x101) inverts  5.7 sec  Err= 0.000000000000000
Test2 - Crout 2000 (101x101) inverts  2.9 sec  Err= 0.000000000000000
Test3 - Crout  2 (1001x1001) inverts  2.8 sec  Err= 0.000000000000000
Test4 - Lapack 2 (1001x1001) inverts  5.4 sec  Err= 0.000000000000000
                             total = 16.8 sec

Results for the REAL(16) variant

Test1 - Gauss 2000 (101x101) inverts 119.8 sec  Err=      0.0000000000000000000000000000001018749071
Test2 - Crout 2000 (101x101) inverts 122.9 sec  Err=      0.0000000000000000000000000000003968958171
Test3 - Crout  2 (1001x1001) inverts 116.6 sec  Err=      0.0000000000000000000000000000002046368750
Test4 - Lapack 2 (1001x1001) inverts 102.2 sec  Err=      0.0000000000000000000000000000033745673898
                             total = 461.6 sec

channel.f90 went from 1s to 97s, induct.f90 from 7s to 1135s, and tfft.f90 from 1.4s to 58s.
> 
>> (2) I think your time would be better used by dealing with your assigned PRs.
> 
> I think I can very well decide for myself where to waste my spare time.

Indeed! However, as soon as you post something to a list, you are interacting (at least you are expecting it) with other people: exchanging opinion, reviewing submitted patches, bike-shedding, … .

Any way, in my mind my comment was an appreciation of your past, recent, and hopefully future contribution to gfortran. If I have upset you, it was not intended and please accept my deepest apologies.

> There were actually times when I enjoyed contributing to
> gfortran and reading this list very much, but recently it's really
> becoming a PITA and I feel like I could spend my time on much nicer
> things ...
> 
> Over and out,
> Janus

Concerning bike-shedding, please don’t add a new syntax for -fdefault-*.

Cheers,

Dominique

  reply	other threads:[~2017-09-22 10:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
2017-09-26  9:47           ` Janus Weil
2017-09-26 14:54       ` David Edelsohn
2017-09-18  9:38 Dominique d'Humières
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=E4300358-3883-49B8-A0AD-1649F69621C6@lps.ens.fr \
    --to=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=janus@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).