public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: Daniel Carrera <dcarrera@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, Fortran] (Coarray) Change declaration of CAF sync functions.
Date: Fri, 10 Jun 2011 11:04:00 -0000	[thread overview]
Message-ID: <4DF1F0A0.6020804@net-b.de> (raw)
In-Reply-To: <4DF1E006.1070504@gmail.com>

On 06/10/2011 11:12 AM, Daniel Carrera wrote:
> This is the patch recently discussed in the GFortran list, now ready 
> for official submission.
> [...]
> 2011-06-07  Daniel Carrera <dcarrera@gmail.com>
>
>     * gfortran.dg/coarray/sync_1.f90: New
>     Test "SYNC ALL", "SYNC MEMORY" and "SYNC IMAGES".
"Test" -> "test for".

> +      /* SYNC ALL           =>   stat == null_pointer_node
> +        SYNC ALL(stat=s)   =>   stat has an integer type
> +
> +         If "stat" has the wrong integer type, use a temp variable of
> +         the right type and later cast the result back into "stat".  */

Intending: The last two lines were space instead of tab-space indented.
Additionally, I think you editor automatically indents lines, which 
causes tailing whitespace in (otherwise) empty lines. I remove those 
(trans-expr.c, mpi.c).

> sync_1.f90:
>
> ! { dg-do run }
> ! { dg-shouldfail "error stop" }

As the ERROR STOP has been removed, the test no longer fails. Hence, 
also the "dg-shouldfail" has to be removed. Otherwise, one gets:

$ make check-gfortran RUNTESTFLAGS='caf.exp=sync_1.f90'
[...]
FAIL: gfortran.dg/coarray/sync_1.f90 -fcoarray=single  -O2  execution test
FAIL: gfortran.dg/coarray/sync_1.f90 -fcoarray=lib  -O2  -lcaf_single 
execution test

It is a frequent problem that one forgets to run the new test cases 
through the testing system, leading to such failures. Or if one did, one 
forgets to do it again after some "trivial" test-case change. ;-)


With those changes, the patch is OK. I have now committed the patch as 
Rev. 174896.

Congratulation to your first GCC patch!

Tobias

  reply	other threads:[~2011-06-10 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10  9:58 Daniel Carrera
2011-06-10 11:04 ` Tobias Burnus [this message]
2011-06-10 11:41   ` Daniel Carrera

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=4DF1F0A0.6020804@net-b.de \
    --to=burnus@net-b.de \
    --cc=dcarrera@gmail.com \
    --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).