From: Mikael Morin <morin-mikael@orange.fr>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fortran: runtime bounds-checking in presence of array constructors [PR31059]
Date: Fri, 8 Sep 2023 11:33:15 +0200 [thread overview]
Message-ID: <4b3ee402-bd92-4e9e-995f-f21cf6d94534@orange.fr> (raw)
In-Reply-To: <fc5895ae-7c98-4bd1-be54-d34a005d6994@gmx.de>
Le 01/09/2023 à 22:48, Harald Anlauf a écrit :
> Hi Mikael,
>
> On 9/1/23 10:41, Mikael Morin via Gcc-patches wrote:
>> May I suggest to handle functions the same way?
>
> I'll have a look at them, but will need to gather a few
> suitable testcases first.
>
I have just opened PR111339
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111339) to track the case
of functions separately.
prev parent reply other threads:[~2023-09-08 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 20:42 Harald Anlauf
2023-09-01 8:41 ` Mikael Morin
2023-09-01 20:48 ` Harald Anlauf
2023-09-08 9:33 ` 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=4b3ee402-bd92-4e9e-995f-f21cf6d94534@orange.fr \
--to=morin-mikael@orange.fr \
--cc=anlauf@gmx.de \
--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).