public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99183] Incompatible Runtime types
Date: Sat, 27 Mar 2021 16:21:56 +0000	[thread overview]
Message-ID: <bug-99183-4-SSXRPbpx2K@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99183-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Priority|P3                          |P4
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-03-27

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Fortran 7.5.0 gives the error

   v = x
      1
Error: Can't convert CLASS(d1) to CLASS(d2) at (1)

but the code is accepted since GCC8.

So the pr seems a 8/9/10/11 regression.

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 20:06 [Bug fortran/99183] New: " drikosev at gmail dot com
2021-02-22 10:48 ` [Bug fortran/99183] " drikosev at gmail dot com
2021-03-27 16:21 ` dominiq at lps dot ens.fr [this message]
2021-10-24 14:27 ` [Bug fortran/99183] [9/10/11 Regression] " dominiq at lps dot ens.fr
2021-10-24 14:41 ` dominiq at lps dot ens.fr
2021-11-16 13:07 ` rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug fortran/99183] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:39 ` [Bug fortran/99183] [11 " rguenth at gcc dot gnu.org
2024-04-25 13:46 ` pault at gcc dot gnu.org
2024-04-25 14:45 ` pault 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-99183-4-SSXRPbpx2K@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).