public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dominique d'Humières" <dominiq@lps.ens.fr>
To: fortran@gcc.gnu.org
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH, committed] PR67826 gcc/fortran/openmp.c:1808: bad test ?
Date: Wed, 11 Nov 2015 10:36:00 -0000	[thread overview]
Message-ID: <9FC9137F-2967-466F-B804-CB1784EFB932@lps.ens.fr> (raw)

I have committed on trunk the following patch as revision r230148 (preapproved by Jakub Jelinek and tested on x86_64-apple-darwin14)

Index: gcc/fortran/ChangeLog
===================================================================
--- gcc/fortran/ChangeLog	(revision 230147)
+++ gcc/fortran/ChangeLog	(working copy)
@@ -1,3 +1,8 @@
+2015-11-11  Dominique d'Humieres <dominiq@lps.ens.fr>
+
+	PR fortran/67826
+	* openmp.c (gfc_omp_udr_find): Fix typo.
+
 2015-11-08  Steven g. Kargl  <kargl@gcc.gnu.org>
 
 	PR fortran/68053
Index: gcc/fortran/openmp.c
===================================================================
--- gcc/fortran/openmp.c	(revision 230147)
+++ gcc/fortran/openmp.c	(working copy)
@@ -1820,7 +1820,7 @@
   for (omp_udr = st->n.omp_udr; omp_udr; omp_udr = omp_udr->next)
     if (omp_udr->ts.type == ts->type
 	|| ((omp_udr->ts.type == BT_DERIVED || omp_udr->ts.type == BT_CLASS)
-	    && (ts->type == BT_DERIVED && ts->type == BT_CLASS)))
+	    && (ts->type == BT_DERIVED || ts->type == BT_CLASS)))
       {
 	if (omp_udr->ts.type == BT_DERIVED || omp_udr->ts.type == BT_CLASS)
 	  {

Dominique

                 reply	other threads:[~2015-11-11 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9FC9137F-2967-466F-B804-CB1784EFB932@lps.ens.fr \
    --to=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).