From: Thomas Koenig <tkoenig@netcologne.de>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: allocatable arrays and -fmax-stack-var-size
Date: Thu, 31 Mar 2022 20:36:37 +0200 [thread overview]
Message-ID: <4f4c6b5f-995f-385a-bacc-59e96090dc97@netcologne.de> (raw)
In-Reply-To: <20220331170747.GA57166@troutmask.apl.washington.edu>
Hi Steve,
> So, it seems that at some point in the past, the option
> -fmax-stack-var-size was expanded to allow the placement
> of an allocatable array into static memory. This has
> a possibly unintended consequence in that automatic
> deallocation of an allocatable array does not (or can
> not) occur.
Sounds like a bug to me, and if your test program worked
in a previous release, it's a regression.
Probably best to open a PR.
Best regards
Thomas
next prev parent reply other threads:[~2022-03-31 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 17:07 Steve Kargl
2022-03-31 18:36 ` Thomas Koenig [this message]
2022-03-31 18:49 ` Steve Kargl
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=4f4c6b5f-995f-385a-bacc-59e96090dc97@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).