public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109209] [13 regression] erroneous error on assignment of alloctables
Date: Mon, 20 Mar 2023 16:54:33 +0000 [thread overview]
Message-ID: <bug-109209-4-CdZbZgeugv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109209-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109209
--- Comment #9 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Jürgen Reuter from comment #4)
>
> module subroutine t3_set_expand (res_set)
> class(t3_set_t), intent(inout) :: res_set
> type(t3_t), dimension(:), allocatable :: history_new
> integer :: s
> s = size (res_set%history)
> allocate (history_new (2 * s))
> history_new(1:s) = res_set%history(1:s)
> call move_alloc (history_new, res_set%history)
> end subroutine t3_set_expand
>
> end module resonances
Actually, the 'module subroutine' here needs to be just 'subroutine'. gfortran
accepts this, nagfor doesn't.
next prev parent reply other threads:[~2023-03-20 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 9:20 [Bug fortran/109209] New: [13.0 " juergen.reuter at desy dot de
2023-03-20 9:29 ` [Bug fortran/109209] [13 " rguenth at gcc dot gnu.org
2023-03-20 11:37 ` juergen.reuter at desy dot de
2023-03-20 14:35 ` juergen.reuter at desy dot de
2023-03-20 15:51 ` juergen.reuter at desy dot de
2023-03-20 15:54 ` juergen.reuter at desy dot de
2023-03-20 16:00 ` juergen.reuter at desy dot de
2023-03-20 16:05 ` juergen.reuter at desy dot de
2023-03-20 16:25 ` juergen.reuter at desy dot de
2023-03-20 16:48 ` burnus at gcc dot gnu.org
2023-03-20 16:54 ` juergen.reuter at desy dot de [this message]
2023-03-20 16:56 ` juergen.reuter at desy dot de
2023-03-20 17:19 ` pault at gcc dot gnu.org
2023-03-20 17:21 ` burnus at gcc dot gnu.org
2023-03-20 17:44 ` pault at gcc dot gnu.org
2023-03-20 17:51 ` pault at gcc dot gnu.org
2023-03-20 17:55 ` anlauf at gcc dot gnu.org
2023-03-20 22:30 ` juergen.reuter at desy dot de
2023-03-21 6:22 ` cvs-commit at gcc dot gnu.org
2023-03-21 7:14 ` 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-109209-4-CdZbZgeugv@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).