public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jerry DeLisle <jvdelisle2@gmail.com>
Subject: Re: [PATCH] PR fortran/85796 - Floating point exception with implied do
Date: Wed, 25 Nov 2020 12:41:51 +0100	[thread overview]
Message-ID: <19eee1a5-7c95-72df-aebf-067aac6092bc@codesourcery.com> (raw)
In-Reply-To: <trinity-6ad13ef8-b4ef-47f8-8ee8-61132f204ae8-1606166336250@3c-app-gmx-bs03>

On 23.11.20 22:18, Harald Anlauf wrote:

> The patch below is based on a previous version by Steve.
> The present version fixes an additional copy&paste error.
>
> Needless to say that it (still!) regtests cleanly on x86_64-pc-linux-gnu.
>
> OK for master?  As it appears safe, OK for backport to at least 10-branch?

LGTM. Thanks for the patch; I think we can backport it to GCC 10.

Tobias

PS: Sorry for the slow patch review

> PR fortran/85796 - Floating point exception with implied do
>
> Catch invalid step=0 in implied do loop within data statements.
>
> gcc/fortran/ChangeLog:
>
>       PR fortran/85796
>       * resolve.c (traverse_data_list): Fix copy&paste errors; catch
>       step=0 in implied do loop.
>
> gcc/testsuite/ChangeLog:
>
>       PR fortran/85796
>       * gfortran.dg/pr85796.f90: New test.
>
-----------------
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-11-25 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 21:18 Harald Anlauf
2020-11-25 11:41 ` Tobias Burnus [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=19eee1a5-7c95-72df-aebf-067aac6092bc@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle2@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).