From: Tobias Burnus <tobias@codesourcery.com>
To: Harald Anlauf <anlauf@gmx.de>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [Patch] Fortran: Fix gfc_conv_gfc_desc_to_cfi_desc with NULL [PR104126]
Date: Wed, 9 Mar 2022 00:34:47 +0100 [thread overview]
Message-ID: <742743fe-d2ab-9cc5-8d94-2585cdd262f3@codesourcery.com> (raw)
In-Reply-To: <e910d4d8-f348-045f-4829-0ecaa286c0a0@gmx.de>
Hi Harald,
On 08.03.22 22:44, Harald Anlauf wrote:
> Am 07.03.22 um 15:16 schrieb Tobias Burnus:
>> Pre-remark: Related NULL, there some accepts-invalid issues, not
>> addressed in this
>> patch. See https://gcc.gnu.org/PR104819
>>
>> This patch fixes an ICE (12 regression) with NULL() that has no MOLD
>> argument.
> the patch does fix the ICE. But given your short pre-remark:
> are you saying that the testcase is invalid, and with the patch
> we silently accept it now?
Sorry for being confusing. I also believe the testcase of the just
committed patch is valid Fortran.
However, when fixing this PR, I was looking at the spec – and saw that
GCC accepts invalid code using NULL(), which is not diagnosed. Those
issues are orthogonal to this patch, except that the accepts-invalid
issues also are about NULL().
Thanks for the review!
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:[~2022-03-08 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 14:16 Tobias Burnus
2022-03-08 21:44 ` Harald Anlauf
2022-03-08 21:44 ` Harald Anlauf
2022-03-08 23:34 ` 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=742743fe-d2ab-9cc5-8d94-2585cdd262f3@codesourcery.com \
--to=tobias@codesourcery.com \
--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).