From: Jerry DeLisle <jvdelisle@charter.net>
To: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Fix contiguous dummy arguments
Date: Sat, 19 Jan 2019 18:00:00 -0000 [thread overview]
Message-ID: <dfeae125-2f92-1797-088c-49435b100105@charter.net> (raw)
In-Reply-To: <fc5fc0c8-9245-365d-dd55-c150a93773cd@netcologne.de>
On 1/19/19 7:05 AM, Thomas Koenig wrote:
> Hello world,
>
> the attached patch fixes handling of contiguous dummy arguments when
> the actual arguments are not contiguous.
>
> The patch to trans-expr.c itself was written by Paul and attached to
> the PR. I just added the test case. Regression-testing revealed some
> failing scan-tree tests due to different code being generated. I put
> corresponding run time tests into the new test case to make sure that no
> wrong code is being generated.
>
> I have also tested the new test case and the compiler with valgrind.
>
> OK for trunk?
>
Looks OK
Jerry
prev parent reply other threads:[~2019-01-19 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 15:05 Thomas Koenig
2019-01-19 18:00 ` Jerry DeLisle [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=dfeae125-2f92-1797-088c-49435b100105@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).