From: Janus Weil <janus@gcc.gnu.org>
To: "Thomas König" <tk@tkoenig.net>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran, committed] Another fallout from clobbering INTENT(OUT) variables
Date: Mon, 24 Sep 2018 08:31:00 -0000 [thread overview]
Message-ID: <CAKwh3qhL1qbxs87TgX4ZobUAzkkbcooc50_h6GSHWRMbBJ3cZg@mail.gmail.com> (raw)
In-Reply-To: <8ea01645-0314-1caf-3143-209c76bdd103@tkoenig.net>
Hi Thomas,
I'm seeing some more fallout from your intent(out) patch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87401
Cheers,
Janus
Am So., 23. Sep. 2018 um 22:23 Uhr schrieb Thomas König <tk@tkoenig.net>:
>
> Hello world,
>
> committed as obvious after regression-testing. Instead of spending
> a lot of work trying to reducing the test case, I used all of it
> (retainging the copyright notice).
>
> Regards
>
> Thomas
>
> 2018-09-23 Thomas Koenig <tkoenig@gcc.gnu.org>
>
> PR fortran/87397
> * gfc_conv_procedure_call: Do not add clobber on INTENT(OUT)
> for variables having the dimension attribute.
>
> 2018-09-23 Thomas Koenig <tkoenig@gcc.gnu.org>
>
> PR fortran/87397
> * gfortran.dg/intent_out_11.f90: New test.
>
prev parent reply other threads:[~2018-09-24 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 7:37 Thomas König
2018-09-24 8:31 ` Janus Weil [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=CAKwh3qhL1qbxs87TgX4ZobUAzkkbcooc50_h6GSHWRMbBJ3cZg@mail.gmail.com \
--to=janus@gcc.gnu.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tk@tkoenig.net \
/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).