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/97652] [11 Regression] New gfortran.dg/pdt_14.f03 failure after g:617695cdc2b3d950f1e4deb5ea85d5cc302943f4
Date: Fri, 06 Nov 2020 15:32:43 +0000 [thread overview]
Message-ID: <bug-97652-4-eZHqaWbOkg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97652-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97652
--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Tobias Burnus
<burnus@gcc.gnu.org>:
https://gcc.gnu.org/g:099857318ca92210e34cfb8975c5c58c00bf1587
commit r10-8989-g099857318ca92210e34cfb8975c5c58c00bf1587
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Fri Nov 6 08:26:51 2020 +0100
Fortran: Fix type-decl for PDT / wrong-code pdt_14.f03 issue [PR97652]
Parameterized derived types are handled in a special way and start with
'Pdt'.
If the 'P' is not uppercase, gfc_get_derived_type (which calls
gfc_get_module_backend_decl) does not find the existing declaration and
builds a new type. The middle end then sees those types as being different
and nonalising, creating an endless loop for pdt_14.f03.
gcc/fortran/ChangeLog:
PR fortran/97652
* module.c (mio_symbol): Fix symbol name for pdt_type.
(cherry picked from commit c283a711c850efaab4fe3bca5ef7200eb854bba1)
next prev parent reply other threads:[~2020-11-06 15:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 8:05 [Bug fortran/97652] New: New pdt14 " hubicka at gcc dot gnu.org
2020-10-31 8:18 ` [Bug fortran/97652] " hubicka at gcc dot gnu.org
2020-11-02 11:30 ` hubicka at gcc dot gnu.org
2020-11-02 13:39 ` [Bug fortran/97652] [11 Regression] New gfortran.dg/pdt_14.f03 " rguenth at gcc dot gnu.org
2020-11-02 13:48 ` rguenth at gcc dot gnu.org
2020-11-02 13:56 ` rguenth at gcc dot gnu.org
2020-11-02 13:58 ` rguenth at gcc dot gnu.org
2020-11-02 14:25 ` rguenth at gcc dot gnu.org
2020-11-02 14:27 ` hubicka at ucw dot cz
2020-11-02 14:29 ` [Bug ipa/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:29 ` rguenth at gcc dot gnu.org
2020-11-02 14:32 ` hubicka at ucw dot cz
2020-11-02 14:51 ` [Bug fortran/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:52 ` rguenth at gcc dot gnu.org
2020-11-03 7:25 ` rguenth at gcc dot gnu.org
2020-11-03 11:15 ` rguenth at gcc dot gnu.org
2020-11-06 7:27 ` cvs-commit at gcc dot gnu.org
2020-11-06 13:01 ` rguenth at gcc dot gnu.org
2020-11-06 15:32 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-06 16:57 ` cvs-commit 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-97652-4-eZHqaWbOkg@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).