From: Harald Anlauf <anlauf@gmx.de>
To: Tobias Burnus <burnus@net-b.de>
Cc: Paul Richard Thomas <paul.richard.thomas@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Aw: Re: [PATCH] PR fortran/99112 - [11 Regression] ICE with runtime diagnostics for SIZE intrinsic function
Date: Sun, 14 Mar 2021 20:54:41 +0100 [thread overview]
Message-ID: <trinity-e3f4867f-453d-46fd-a1b6-1ec5c98893b3-1615751681246@3c-app-gmx-bap38> (raw)
In-Reply-To: <e876c57f-b6ad-83ce-b4d7-b2287b3b7350@net-b.de>
Hi Tobias,
> I do not see any reason why 'tmp' is replaced by 'temp' in this
> code. Also for doing patch archeology, it helps if there are no
> changes unless it makes sense. Adding an -e- does not count ;-)
>
> Hence, OK with that change.
I've corrected that. This also reduces the size of the patch.
> Regarding the change:
> gfc_conv_intrinsic_size (gfc_se * se, gfc_expr * expr)
>
> It looks as if the pointer/check is done for
> size(dt%foo%bar)
> for the 'bar' component' but shouldn't it also be
> done for each part ref, if it is a pointer/allocatable?
> (i.e. 'dt', 'foo' and 'bar'?
>
> That's independent of the current patch.
>
> Additionally, as there are a lot of special cases for
> CLASS – I wonder whether there also needs to be a special
> case for
> size(dt%foo%class)
> ?
>
> In particular, the following does ICE for me:
This ICEs even without any checks enabled and is now:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99585
> > P.S.: I couldn't find a Changelog entry that uses co-authors. Is the
> > version
> > below correct?
> ...
> > Co-authored-by: Paul Thomas <pault@gcc.gnu.org>
>
> I think you have two options: either the GIT way – as you did (although I think the
> GIT way usually only has one and not two spaces before the email).
>
> I did not see it in the commit logs, but it is used in the
> testcases for the change-log generator, see: contrib/gcc-changelog/test_patches.txt
I've done it as described above. In the git log I see the co-author, while
> git show -1 | ./contrib/gcc-changelog/git_check_commit.py -p
produces:
Checking c2d7c39fcb8a3cb67600cdb6fde49ecb0e951589: OK
------ gcc/fortran/ChangeLog ------
2021-03-14 Harald Anlauf <anlauf@gmx.de>
Paul Thomas <pault@gcc.gnu.org>
etc. Nice!
Thanks for the review. But as your testcase shows, we're not finished yet...
Thanks,
Harald
prev parent reply other threads:[~2021-03-14 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 20:43 Harald Anlauf
2021-03-13 8:58 ` Paul Richard Thomas
2021-03-14 10:56 ` Tobias Burnus
2021-03-14 19:54 ` Harald Anlauf [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=trinity-e3f4867f-453d-46fd-a1b6-1ec5c98893b3-1615751681246@3c-app-gmx-bap38 \
--to=anlauf@gmx.de \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@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).