public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@archaeologic.codes>
To: Jerry D <jvdelisle2@gmail.com>
Cc: Paul Richard Thomas via Fortran <fortran@gcc.gnu.org>
Subject: Re: Finalization
Date: Wed, 2 Nov 2022 18:39:23 -0700	[thread overview]
Message-ID: <CAHS2gMwrYfXGu1hGPM7TUC4yjUyYqKFBVTP-dyzEGrqxAtiD7w@mail.gmail.com> (raw)
In-Reply-To: <e319f9df-cd66-416a-4375-9e6ec74a95ca@gmail.com>

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

Thanks for asking this, Jerry!

Sourcery Institute has a (small) amount of funding that can be offered for
this work in case that helps.

Damian

On Wed, Nov 2, 2022 at 6:32 PM Jerry D via Fortran <fortran@gcc.gnu.org>
wrote:

> Hi Paul,
>
> Long time no chat.  I hope you and yours are well.
>
> I was planning to retire early next year, but with the economy going
> south on us I am going to hold off a bit.  What a crazy world we are in!
>
> I thought I would drop you a note when I noticed a gfortran finalization
> bug 107489.  Then Steve Kargl mentioned the previous patch you had done
> a lot of work on.  I don't remember if that ever went into trunk or was
> pending some interpretation.
>
> I tried to apply the patch I found and of course it is broken here and
> there.  I don't know if you have been keeping it alive or not relative
> to latest trunk.  So, I thought I would ask privately and at the same
> time see how you are doing?
>
> Cheers always Paul,
>
> Jerry
>

      reply	other threads:[~2022-11-03  1:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  1:31 Finalization Jerry D
2022-11-03  1:39 ` Damian Rouson [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=CAHS2gMwrYfXGu1hGPM7TUC4yjUyYqKFBVTP-dyzEGrqxAtiD7w@mail.gmail.com \
    --to=damian@archaeologic.codes \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    /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).