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/99819] [9/10/11/12 Regression] ICE in gfc_defer_symbol_init, at fortran/trans-decl.c:841
Date: Sat, 28 Aug 2021 18:28:32 +0000 [thread overview]
Message-ID: <bug-99819-4-YhuDqr0GBV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99819-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99819
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:
https://gcc.gnu.org/g:be64e725111fdb9caa05374823b4423b8ab49dc7
commit r11-8936-gbe64e725111fdb9caa05374823b4423b8ab49dc7
Author: Paul Thomas <pault@gcc.gnu.org>
Date: Thu May 6 14:41:33 2021 +0100
Fortran: Assumed and explicit size class arrays [PR46691/99819].
2021-05-06 Paul Thomas <pault@gcc.gnu.org>
gcc/fortran/ChangeLog
PR fortran/46691
PR fortran/99819
* class.c (gfc_build_class_symbol): Remove the error that
disables assumed size class arrays. Class array types that are
not deferred shape or assumed rank are given a unique name and
placed in the procedure namespace.
* trans-array.c (gfc_trans_g77_array): Obtain the data pointer
for class arrays.
(gfc_trans_dummy_array_bias): Suppress the runtime error for
extent violations in explicit shape class arrays because it
always fails.
* trans-expr.c (gfc_conv_procedure_call): Handle assumed size
class actual arguments passed to non-descriptor formal args by
using the data pointer, stored as the symbol's backend decl.
gcc/testsuite/ChangeLog
PR fortran/46691
PR fortran/99819
* gfortran.dg/class_dummy_6.f90: New test.
* gfortran.dg/class_dummy_7.f90: New test.
(cherry picked from commit a2c593009fef1564dbef2237ee71e9fd08f5361e)
next prev parent reply other threads:[~2021-08-28 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 19:35 [Bug fortran/99819] New: [9/10/11 " gscfq@t-online.de
2021-03-30 13:08 ` [Bug fortran/99819] " rguenth at gcc dot gnu.org
2021-03-30 19:43 ` anlauf at gcc dot gnu.org
2021-05-02 17:05 ` [Bug fortran/99819] [9/10/11/12 " pault at gcc dot gnu.org
2021-05-04 12:32 ` rguenth at gcc dot gnu.org
2021-05-06 13:44 ` cvs-commit at gcc dot gnu.org
2021-06-01 8:20 ` rguenth at gcc dot gnu.org
2021-08-27 20:44 ` anlauf at gcc dot gnu.org
2021-08-28 18:28 ` cvs-commit at gcc dot gnu.org [this message]
2021-08-28 18:30 ` [Bug fortran/99819] [9/10 " anlauf at gcc dot gnu.org
2021-08-30 20:13 ` cvs-commit at gcc dot gnu.org
2021-08-30 20:15 ` [Bug fortran/99819] [9 " anlauf at gcc dot gnu.org
2021-09-06 19:03 ` cvs-commit at gcc dot gnu.org
2021-09-06 19:04 ` anlauf 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-99819-4-YhuDqr0GBV@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).