From: Tobias Burnus <tobias@codesourcery.com>
To: Sandra Loosemore <sandra@codesourcery.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2, Fortran] [PR libfortran/101317] Bind(c): Improve error checking in CFI_* functions
Date: Mon, 26 Jul 2021 09:35:30 +0200 [thread overview]
Message-ID: <d3e0a7c9-9dd9-2cc5-a927-27ab51835606@codesourcery.com> (raw)
In-Reply-To: <28519de9-3fca-7c94-1edf-5d920d3fccdf@codesourcery.com>
Hi Sandra,
On 25.07.21 06:11, Sandra Loosemore wrote:
>> Congratulation – we have found a bug in the spec, which is also
>> present in the current draft (21-007). I have now written to J3:
>> https://mailman.j3-fortran.org/pipermail/j3/2021-July/013189.html
>
> That discussion seems to have wandered off into some other direction
> so I'm not sure whether it really clarifies this problem.
I concur. I do hope that it will be at some point discussed and clarified.
But for now:
> For the purposes of this patch I have left in the test for elem_len >
> 0 in CFI_establish where the standard explicitly has that requirement
> and removed it from the other functions where I'd added it just to be
> consistent.
I think that makes sense.
> OK, I have done that throughout the file, and also made the wording
> change you asked for. While I was at it, I went through all the
> diagnostic messages in the file and simplified the wording of a few
> other messages as well, fixed typos and inconsistent capitalization
> and missing punctuation and things like that.
Thanks!
> Here's a new patch.
LGTM.
Thanks,
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
prev parent reply other threads:[~2021-07-26 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 0:49 [PATCH, " Sandra Loosemore
2021-07-21 17:26 ` Tobias Burnus
2021-07-21 18:01 ` Sandra Loosemore
2021-07-22 7:54 ` Tobias Burnus
2021-07-25 4:11 ` [PATCH v2, " Sandra Loosemore
2021-07-26 7:35 ` Tobias Burnus [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=d3e0a7c9-9dd9-2cc5-a927-27ab51835606@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sandra@codesourcery.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).