public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/103576] [12 Regression] gcc/fortran/openmp.c:7556:8: warning: overlapping comparisons always evaluate to true [-Wtautological-overlap-compare] since r12-5793-g689407ef916503b2f5a3c8c07fe7d5ab1913f956
Date: Mon, 06 Dec 2021 10:05:50 +0000 [thread overview]
Message-ID: <bug-103576-4-uJy9rk5BN6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103576-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103576
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #1)
> I suppose it should be:
> expr->ts.type != foo && expr->ts.type != bar ...
Rather the following. There are some more fixes I should do in this area; I
added this patch on top of it. (Remaining: some more testcase writing and
testcase cleanup.)
--- a/gcc/fortran/openmp.c
+++ b/gcc/fortran/openmp.c
@@ -7555,4 +7555,4 @@ is_scalar_intrinsic_expr (gfc_expr *expr, bool
must_be_var, bool
- && (expr->ts.type != BT_INTEGER
- || expr->ts.type != BT_REAL
- || expr->ts.type != BT_COMPLEX
- || expr->ts.type != BT_LOGICAL));
+ && (expr->ts.type == BT_INTEGER
+ || expr->ts.type == BT_REAL
+ || expr->ts.type == BT_COMPLEX
+ || expr->ts.type == BT_LOGICAL));
next prev parent reply other threads:[~2021-12-06 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:54 [Bug fortran/103576] New: " marxin at gcc dot gnu.org
2021-12-06 9:56 ` [Bug fortran/103576] " marxin at gcc dot gnu.org
2021-12-06 10:05 ` burnus at gcc dot gnu.org [this message]
2021-12-13 11:38 ` cvs-commit at gcc dot gnu.org
2021-12-13 11:40 ` burnus at gcc dot gnu.org
2021-12-14 6:21 ` cvs-commit 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-103576-4-uJy9rk5BN6@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).