public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97655] New: gcc/fortran/openmp.c:4133: possible cut'n'paste error ?
Date: Sat, 31 Oct 2020 16:26:10 +0000	[thread overview]
Message-ID: <bug-97655-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 97655
           Summary: gcc/fortran/openmp.c:4133: possible cut'n'paste error
                    ?
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

gcc/fortran/openmp.c:4133:12: style: Expression is always false because 'else
if' condition matches previous condition at line 4131. [multiCondition]

Source code is

          if (c->atomic_op == GFC_OMP_ATOMIC_READ)
            c->memorder = OMP_MEMORDER_ACQUIRE;
          else if (c->atomic_op == GFC_OMP_ATOMIC_READ)
            c->memorder = OMP_MEMORDER_RELEASE;
          else
            c->memorder = OMP_MEMORDER_ACQ_REL;

             reply	other threads:[~2020-10-31 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31 16:26 dcb314 at hotmail dot com [this message]
2020-10-31 16:54 ` [Bug fortran/97655] " dcb314 at hotmail dot com
2020-10-31 16:56 ` jakub at gcc dot gnu.org
2020-11-01 12:15 ` burnus at gcc dot gnu.org
2020-11-02  8:27 ` jakub at gcc dot gnu.org
2020-11-02  8:29 ` marxin at gcc dot gnu.org
2020-11-02 12:08 ` cvs-commit at gcc dot gnu.org
2020-11-02 12:09 ` burnus 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-97655-4@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).