public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickpapior at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99355] -freal-X-real-Y -freal-Z-real-X promotes Z to Y
Date: Wed, 03 Mar 2021 09:16:42 +0000	[thread overview]
Message-ID: <bug-99355-4-TBPL5RrcUD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99355-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99355

--- Comment #3 from Nick <nickpapior at gmail dot com> ---
Yes, real*4 -> real*16. 

I agree that the option semantics are not clear. However, the documentation
says:

Promote all REAL(KIND=M) entities to REAL(KIND=N) entities. If REAL(KIND=N) is
unavailable, then an error will be issued. All other real kind types are
unaffected by this option. These options should be used with care and may not
be suitable for your codes. Areas of possible concern include calls to external
procedures, alignment in EQUIVALENCE and/or COMMON, generic interfaces, BOZ
literal constant conversion, and I/O. Inspection of the intermediate
representation of the translated Fortran code, produced by
-fdump-tree-original, is suggested.

>From this I read that no *double* promotions are done. However, the text isn't
clear either.

I would just not assume that *everything* gets promoted, especially since there
is a -freal-4-real-16 option, so users can already be explicit.


I guess this also applies to the -finteger-4-integer-8 and friends (untested)

  parent reply	other threads:[~2021-03-03  9:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  7:00 [Bug fortran/99355] New: " nickpapior at gmail dot com
2021-03-03  7:00 ` [Bug fortran/99355] " nickpapior at gmail dot com
2021-03-03  8:31 ` rguenth at gcc dot gnu.org
2021-03-03  9:16 ` nickpapior at gmail dot com [this message]
2021-03-03 14:38 ` burnus at gcc dot gnu.org
2021-03-03 20:39 ` nickpapior at gmail dot com
2021-03-04  7:20 ` cvs-commit at gcc dot gnu.org
2021-03-04  7:20 ` burnus at gcc dot gnu.org
2021-03-04 12:02 ` dominiq at lps dot ens.fr
2021-03-04 12:37 ` burnus at gcc dot gnu.org
2021-03-04 13:03 ` dominiq at lps dot ens.fr
2021-03-04 14:01 ` burnus at gcc dot gnu.org
2021-03-04 14:13 ` burnus at gcc dot gnu.org
2021-03-04 14:41 ` dominiq at lps dot ens.fr
2021-03-04 16:04 ` burnus at gcc dot gnu.org
2021-03-04 16:24 ` dominiq at lps dot ens.fr
2021-03-04 22:32 ` burnus at gcc dot gnu.org
2021-03-05  9:43 ` cvs-commit at gcc dot gnu.org
2021-03-05  9:46 ` burnus at gcc dot gnu.org

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=bug-99355-4-TBPL5RrcUD@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).