public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <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: Thu, 04 Mar 2021 14:13:55 +0000 [thread overview]
Message-ID: <bug-99355-4-N2ihLfxNsW@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 #12 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Additional patch – my need some cleanup & check whether the
other flags agree with the description. However, it should
match the implementation:
--- a/gcc/fortran/invoke.texi
+++ b/gcc/fortran/invoke.texi
@@ -519,8 +519,13 @@ representation of the translated Fortran code, produced by
@opindex @code{freal-8-real-16}
@cindex options, real kind type promotion
Promote all @code{REAL(KIND=M)} entities to @code{REAL(KIND=N)} entities.
-If @code{REAL(KIND=N)} is unavailable, then an error will be issued.
-All other real kind types are unaffected by this option.
+If @code{REAL(KIND=N)} is unavailable, then an error will be issued;
+the real-4 flags also affect the default real kind, the real-8 flag also
+the double-precision real kind. All other real kind types are
+unaffected by this option. For real literal constants, the promoted
+values are used for the default kinds and a specified kind value is
+promoted to the new value. Note that when using @code{REAL(KIND=KIND(1.0))}
+the literal is first promoted and then the result is promoted again.
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 @code{EQUIVALENCE} and/or @code{COMMON}, generic interfaces,
next prev parent reply other threads:[~2021-03-04 14:13 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
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 [this message]
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-N2ihLfxNsW@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).