public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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 07:20:10 +0000 [thread overview]
Message-ID: <bug-99355-4-59Q1STBqbA@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 #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>:
https://gcc.gnu.org/g:d259ab15761de2d938c24abfba9cdcd2fef91655
commit r11-7501-gd259ab15761de2d938c24abfba9cdcd2fef91655
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Thu Mar 4 08:18:31 2021 +0100
Fortran: Fix -freal-{4,8}-real* handling [PR99355]
Avoid chain kind conversion for, e.g., -freal-4-real-8 -freal-8-real-10.
Note that gfc_default_double_kind/gfc_default_double_kind already
honors the -freal flags.
gcc/fortran/ChangeLog:
PR fortran/99355
* decl.c (gfc_match_old_kind_spec, gfc_match_kind_spec): Avoid
redoing kind conversions.
* primary.c (match_real_constant): Likewise.
gcc/testsuite/ChangeLog:
PR fortran/99355
* gfortran.dg/real4-10-real8-10.f90: New test.
* gfortran.dg/real4-10-real8-16.f90: New test.
* gfortran.dg/real4-10-real8-4.f90: New test.
* gfortran.dg/real4-10.f90: New test.
* gfortran.dg/real4-16-real8-10.f90: New test.
* gfortran.dg/real4-16-real8-16.f90: New test.
* gfortran.dg/real4-16-real8-4.f90: New test.
* gfortran.dg/real4-16.f90: New test.
* gfortran.dg/real4-8-real8-10.f90: New test.
* gfortran.dg/real4-8-real8-16.f90: New test.
* gfortran.dg/real4-8-real8-4.f90: New test.
* gfortran.dg/real4-8.f90: New test.
* gfortran.dg/real8-10.f90: New test.
* gfortran.dg/real8-16.f90: New test.
* gfortran.dg/real8-4.f90: New test.
next prev parent reply other threads:[~2021-03-04 7:20 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 [this message]
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-59Q1STBqbA@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).