From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 59B9A3850414; Tue, 18 Aug 2020 19:49:16 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 59B9A3850414
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1597780156;
 bh=cEb+1uFIzUb5n9geZ41sk4lUXFEx2OgmlOuGLIbDEVs=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=vFGqZ804i7TEUT7xUA5DCw9s4smPc24GA7yr9RsZ+ZWqNrvAOC89+wPYtqp/q5MWr
 IyO8+J6Bv2H9gK/k3/fCjI+yk6tI4GNUV369qpnH94FdvPiMvnvonHSOxUBwcoQq/N
 4ml17ryMaLL3NmmiJbt3WHhF2RYCyq6iotuOAFyU=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96613] SIGFPE on min1() with -ffpe-trap=invalid switch
Date: Tue, 18 Aug 2020 19:49:16 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-96613-4-pGzt9K6cA9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-96613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-96613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2020 19:49:16 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96613

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:3c04bd60e56da399a441f73ebb687b5039b9cf3f

commit r11-2746-g3c04bd60e56da399a441f73ebb687b5039b9cf3f
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Aug 18 21:48:56 2020 +0200

    PR fortran/96613,96686 - Fix type/kind issues, temporaries evaluating
MIN/MAX

    When evaluating functions of the MIN/MAX variety inline, use a temporary
    of appropriate type and kind, and convert to the result type at the end.
    In the case of allowing for the GNU extensions to MIN/MAX, derive the
    result kind consistently during simplificaton.

    Furthermore, the Fortran standard requires type and kind of arguments to
    the MIN/MAX intrinsics to all have the same type and kind.  While a GNU
    extension accepts kind differences for integer and real arguments which
    seems to have been used in legacy code, there is no reason to allow
    different character kinds.  We now reject the latter unconditionally.

    gcc/fortran/ChangeLog:

            * check.c (check_rest): Reject MIN/MAX character arguments of
            different kind.
            * simplify.c (min_max_choose): The simplification result shall
            have the highest kind value of the arguments.
            * trans-intrinsic.c (gfc_conv_intrinsic_minmax): Choose type and
            kind of intermediate by looking at all arguments, not the resul=
t.

    gcc/testsuite/ChangeLog:

            * gfortran.dg/minmax_char_3.f90: New test.
            * gfortran.dg/min_max_kind.f90: New test.
            * gfortran.dg/pr96613.f90: New test.=