public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [patch, wwwdocs] Mention finalization
Date: Sun, 19 Mar 2023 11:41:51 +0000	[thread overview]
Message-ID: <CAGkQGi+HBn5JYDmNmZ5n=Wg2x-Zd4qwxW-ph=mq0c7dYEqO9KQ@mail.gmail.com> (raw)
In-Reply-To: <24a27aff-54ee-442b-c150-9617a1ab4f19@netcologne.de>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

Hi Thomas,

Thanks for that! I think that your one-liner says it all :-)

There are three PRs left open that PR37336 depends on:
PR65347: Is partially fixed. The F2003/8 feature of finalization of a
structure constructor within an array constructor doesn't work. I wonder if
a compile option -finalize-constructors might not be better than
-std=f2003/8?
PR84472: I need to investigate if it is fixed or not. It behaves like one
of the other brands, which complains about a double free. The other brand
does not have this problem. At one stage, I nulled pointer components
before finalization of a function result but removed it because it is not
required by the standard. It might well be a good idea, just on the grounds
that smart-pointers and resource managers seem to be the main real-life use
of finalization and pointer components loom large with them.
PR91316: An impure final call is allowed within a pure procedure at the
moment. Malcolm Cohen convinced me that this should be disallowed.

If the finalization patch has survived a few weeks on mainline without
causing problems, I am inclined to backport to 12-branch. Would that be
acceptable to one and all?

Cheers

Paul


On Sun, 19 Mar 2023 at 08:15, Thomas Koenig via Fortran <fortran@gcc.gnu.org>
wrote:

> Hi,
>
> the sentence below seems a bit short for such a huge undertaking,
> but I could not think of anything else to day.
>
> Tested with "tidy -e".
>
> OK for wwwdocs?
>
> Best regards
>
>         Thomas
>
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index c8d757b6..a4b71ffa 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -373,7 +373,12 @@ a work-in-progress.</p>
>
>   <!-- <h3 id="d">D</h3> -->
>
> -<!-- <h3 id="fortran">Fortran</h3> -->
> +<h3 id="fortran">Fortran</h3>
> +<ul>
> +  <li>
> +    Finalization is now fully supported.
> +  </li>
> +</ul>
>
>   <!-- <h3 id="go">Go</h3> -->
>


-- 
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein

      reply	other threads:[~2023-03-19 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  8:15 Thomas Koenig
2023-03-19 11:41 ` Paul Richard Thomas [this message]

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='CAGkQGi+HBn5JYDmNmZ5n=Wg2x-Zd4qwxW-ph=mq0c7dYEqO9KQ@mail.gmail.com' \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).