public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107062] [13 regression] gfortran.dg/ieee/fma_1.f90 fails after r13-2577-g7c4c65d11469d2
Date: Wed, 28 Sep 2022 07:23:14 +0000	[thread overview]
Message-ID: <bug-107062-4-ALLkBCyvJu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107062-4@http.gcc.gnu.org/bugzilla/>

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

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-09-28
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #1 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Can you run this on the target, and post the output here?

$ cat a.f90 
  use ieee_arithmetic
  integer, parameter :: k1 = &
    max(ieee_selected_real_kind(precision(0.d0) + 1), kind(0.))
  integer, parameter :: k2 = &
    max(ieee_selected_real_kind(precision(0._k1) + 1), kind(0.d0))

  print *, k1, k2
  end
$ gfortran a.f90 && ./a.out
          16           8

  reply	other threads:[~2022-09-28  7:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 21:04 [Bug fortran/107062] New: " seurer at gcc dot gnu.org
2022-09-28  7:23 ` fxcoudert at gcc dot gnu.org [this message]
2022-09-28 14:57 ` [Bug fortran/107062] " seurer at gcc dot gnu.org
2022-09-28 15:24 ` fxcoudert at gcc dot gnu.org
2022-09-28 15:33 ` fxcoudert at gcc dot gnu.org
2022-09-28 16:52 ` seurer at gcc dot gnu.org
2022-09-29  8:11 ` rguenth at gcc dot gnu.org
2022-10-03  7:30 ` fxcoudert at gcc dot gnu.org
2022-10-03  7:30 ` fxcoudert 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-107062-4-ALLkBCyvJu@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).