From: Mikael Morin <morin-mikael@orange.fr>
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2 0/9] fortran: clobber fixes [PR41453]
Date: Mon, 10 Oct 2022 20:58:40 +0200 [thread overview]
Message-ID: <e78c9f2e-ed76-d32a-f909-2addf70f36b6@orange.fr> (raw)
In-Reply-To: <c72f21c2-5a23-f726-e08e-bd419a82ec4c@orange.fr>
Le 23/09/2022 à 09:54, Mikael Morin a écrit :
> Le 22/09/2022 à 22:42, Harald Anlauf via Fortran a écrit :
>> This LGTM. It also fixes a regression introduced with r9-3030 :-)
>> If you think that this set (1-3) is backportable, feel free to do so.
>>
> Yes, 2 and 3 are worth backporting, I will see how dependent they are on 1.
>
I'm going to backport 1-3 as you suggested, it's so much easier.
prev parent reply other threads:[~2022-10-10 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 20:15 Mikael Morin
2022-09-18 20:15 ` [PATCH v2 1/9] fortran: Move the clobber generation code Mikael Morin
2022-09-18 20:15 ` [PATCH v2 2/9] fortran: Fix invalid function decl clobber ICE [PR105012] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 3/9] fortran: Move clobbers after evaluation of all arguments [PR106817] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 4/9] fortran: Support clobbering with implicit interfaces [PR105012] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 5/9] fortran: Support clobbering of reference variables [PR41453] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 6/9] fortran: Support clobbering of SAVE variables [PR87395] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 7/9] fortran: Support clobbering of ASSOCIATE variables [PR87397] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 8/9] fortran: Support clobbering of allocatables and pointers [PR41453] Mikael Morin
2022-09-18 20:15 ` [PATCH v2 9/9] fortran: Support clobbering of derived types [PR41453] Mikael Morin
[not found] ` <tgihce$hvi$1@ciao.gmane.io>
2022-09-23 7:54 ` [PATCH v2 0/9] fortran: clobber fixes [PR41453] Mikael Morin
2022-09-25 12:53 ` Mikael Morin
2022-10-10 18:58 ` Mikael Morin [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=e78c9f2e-ed76-d32a-f909-2addf70f36b6@orange.fr \
--to=morin-mikael@orange.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).