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/102745] CLASS → TYPE check fails after RESHAPE
Date: Tue, 19 Oct 2021 08:52:47 +0000 [thread overview]
Message-ID: <bug-102745-4-Z167UGuL4T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102745-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102745
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Tobias Burnus
<burnus@gcc.gnu.org>:
https://gcc.gnu.org/g:3de82c6c36fea8fad7145b62ccb3a7c06d1f3c51
commit r11-9173-g3de82c6c36fea8fad7145b62ccb3a7c06d1f3c51
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon Oct 18 09:49:05 2021 +0200
Fortran: Fix CLASS conversion check [PR102745]
PR fortran/102745
gcc/fortran/ChangeLog
* intrinsic.c (gfc_convert_type_warn): Fix checks by checking CLASS
and do typcheck in correct order for type extension.
* misc.c (gfc_typename): Print proper not internal CLASS type name.
gcc/testsuite/ChangeLog
* gfortran.dg/class_72.f90: New.
(cherry picked from commit 017665f63047ce47b087b0b283548a60e5abf3d2)
next prev parent reply other threads:[~2021-10-19 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:16 [Bug fortran/102745] New: " burnus at gcc dot gnu.org
2021-10-18 7:49 ` [Bug fortran/102745] " cvs-commit at gcc dot gnu.org
2021-10-19 8:52 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-19 10:38 ` burnus at gcc dot gnu.org
2021-11-23 8:03 ` pinskia 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-102745-4-Z167UGuL4T@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).