public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107272] ICE in gfc_compare_string and others (related to pr107217)
Date: Mon, 17 Oct 2022 17:26:07 +0000	[thread overview]
Message-ID: <bug-107272-4-SZT7NNm0qT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107272-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:34cecde675be67543b386b593132ce8b1bb0a3ab

commit r13-3339-g34cecde675be67543b386b593132ce8b1bb0a3ab
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Sun Oct 16 20:32:27 2022 +0200

    Fortran: check type of operands of logical operations, comparisons
[PR107272]

    gcc/fortran/ChangeLog:

            PR fortran/107272
            * arith.cc (gfc_arith_not): Operand must be of type BT_LOGICAL.
            (gfc_arith_and): Likewise.
            (gfc_arith_or): Likewise.
            (gfc_arith_eqv): Likewise.
            (gfc_arith_neqv): Likewise.
            (gfc_arith_eq): Compare consistency of types of operands.
            (gfc_arith_ne): Likewise.
            (gfc_arith_gt): Likewise.
            (gfc_arith_ge): Likewise.
            (gfc_arith_lt): Likewise.
            (gfc_arith_le): Likewise.

    gcc/testsuite/ChangeLog:

            PR fortran/107272
            * gfortran.dg/pr107272.f90: New test.

  parent reply	other threads:[~2022-10-17 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 20:24 [Bug fortran/107272] New: " anlauf at gcc dot gnu.org
2022-10-16 18:48 ` [Bug fortran/107272] " anlauf at gcc dot gnu.org
2022-10-17 17:26 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-17 17:32 ` anlauf at gcc dot gnu.org

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=bug-107272-4-SZT7NNm0qT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).