public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Andre Vehreschild <vehre@gmx.de>,
	GCC-Fortran-ML <fortran@gcc.gnu.org>,
	GCC-Patches-ML <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, fortran, coarray] Fix obvious typo in co_broadcast's argument assembly
Date: Tue, 18 Aug 2020 19:14:30 +0200	[thread overview]
Message-ID: <3823e678-8ece-6bd1-678c-4ff39c8b653c@codesourcery.com> (raw)
In-Reply-To: <20200818190423.6171bf57@vepi2>

On 8/18/20 7:04 PM, Andre Vehreschild wrote:

> attached patch fixes an obvious typo in the routine gathering arguments for
> co_broadcast().  See pr94958 for a detailed analysis, please.

LGTM – except that I do not like the ChangeLog entry.

It sounds like a mispelling in terms of a comment or
error message. How about "Using the correct variable."
– or something like that?

You could also consider adding a libcaf_single test case,
given that you wrote one (see PR)...

Thanks for the patch!

Tobias

> gcc/fortran/ChangeLog:
>
> 2020-08-18  Andre Vehreschild<vehre@gcc.gnu.org>
>
>       PR fortran/94958
>       * trans-array.c (gfc_bcast_alloc_comp): Fix typo.
>
>
> pr94958.patch
>
> diff --git a/gcc/fortran/trans-array.c b/gcc/fortran/trans-array.c
> index 7a1b2fc74c9..73a45cd2dcf 100644
> --- a/gcc/fortran/trans-array.c
> +++ b/gcc/fortran/trans-array.c
> @@ -9732,7 +9732,7 @@ gfc_bcast_alloc_comp (gfc_symbol *derived, gfc_expr *expr, int rank,
>     args.image_index = image_index;
>     args.stat = stat;
>     args.errmsg = errmsg;
> -  args.errmsg = errmsg_len;
> +  args.errmsg_len = errmsg_len;
>
>     if (rank == 0)
>       {
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter

  reply	other threads:[~2020-08-18 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 17:04 Andre Vehreschild
2020-08-18 17:14 ` Tobias Burnus [this message]
2020-08-18 17:27   ` Andre Vehreschild
2020-08-20 15:53     ` Andre Vehreschild

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=3823e678-8ece-6bd1-678c-4ff39c8b653c@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vehre@gmx.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).