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/57871] gfortran -freal-4-real-16 gives wrong result for selected_real_kind(1)
Date: Fri, 05 Mar 2021 09:43:50 +0000	[thread overview]
Message-ID: <bug-57871-4-8iQnoJc4Fc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57871-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 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:80cf2facbbdafed159b326d83f7cf3999c3df8d0

commit r11-7519-g80cf2facbbdafed159b326d83f7cf3999c3df8d0
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Fri Mar 5 10:43:11 2021 +0100

    Fortran: Follow fixes to -freal-{4,8}-real* handling [PR99355,PR57871]

    gcc/fortran/ChangeLog:

            PR fortran/99355
            PR fortran/57871
            * invoke.texi (-freal{4,8}-real-*): Extend description.
            * primary.c (match_real_constant): Also promote real literals
            with '_kind' number.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/real4-10-real8-10.f90: Add check for real literals
            with '_kind' number.
            * gfortran.dg/real4-10-real8-16.f90: Likewise.
            * gfortran.dg/real4-10-real8-4.f90: Likewise.
            * gfortran.dg/real4-10.f90: Likewise.
            * gfortran.dg/real4-16-real8-10.f90: Likewise.
            * gfortran.dg/real4-16-real8-16.f90: Likewise.
            * gfortran.dg/real4-16-real8-4.f90: Likewise.
            * gfortran.dg/real4-16.f90: Likewise.
            * gfortran.dg/real4-8-real8-10.f90: Likewise.
            * gfortran.dg/real4-8-real8-16.f90: Likewise.
            * gfortran.dg/real4-8-real8-4.f90: Likewise.
            * gfortran.dg/real4-8.f90: Likewise.
            * gfortran.dg/real8-10.f90: Likewise.
            * gfortran.dg/real8-16.f90: Likewise.
            * gfortran.dg/real8-4.f90: Likewise.

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 23:38 [Bug fortran/57871] New: " john.harper at vuw dot ac.nz
2013-07-10 13:07 ` [Bug fortran/57871] " dominiq at lps dot ens.fr
2013-07-10 17:42 ` kargl at gcc dot gnu.org
2013-07-10 20:02 ` sgk at troutmask dot apl.washington.edu
2013-07-10 21:31 ` harper at msor dot vuw.ac.nz
2013-07-11 22:30 ` harper at msor dot vuw.ac.nz
2013-07-11 22:51 ` sgk at troutmask dot apl.washington.edu
2013-11-25  0:59 ` kargl at gcc dot gnu.org
2021-03-04 11:59 ` dominiq at lps dot ens.fr
2021-03-05  9:43 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-05  9:53 ` burnus at gcc dot gnu.org
2021-03-07 13:19 ` dominiq at lps dot ens.fr

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-57871-4-8iQnoJc4Fc@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).