public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97176] Cannot return deferred length strings when using -fno-automatic
Date: Wed, 23 Sep 2020 19:35:49 +0000 [thread overview]
Message-ID: <bug-97176-4-ZKbBxUSYSE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97176-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97176
--- Comment #2 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #1)
> Workaround 3.
>
> Explicitly give entities the SAVE attribute whereby your
> testfunc() becomes
>
> function testfunc(string) result(res)
> character(:), allocatable, save :: res
> character(*), intent(in) :: string
> res = string
> end function testfunc
That is explicit standard violation.
Adding a blank SAVE statement in the function body seems to work as expected,
so a user who believes in -fno-automatic may call it a gfortran bug.
Personally, I'd recommend:
Workaround 4.
Never use -fno-automatic.
next prev parent reply other threads:[~2020-09-23 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 10:01 [Bug fortran/97176] New: " jeremy at jeremysanders dot net
2020-09-23 16:43 ` [Bug fortran/97176] " kargl at gcc dot gnu.org
2020-09-23 19:35 ` anlauf at gcc dot gnu.org [this message]
2020-09-24 6:44 ` jeremy at jeremysanders dot net
2020-10-05 12:23 ` dominiq at lps dot ens.fr
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-97176-4-ZKbBxUSYSE@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).