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/67826] New: gcc/fortran/openmp.c:1808: bad test ?
Date: Fri, 02 Oct 2015 20:32:00 -0000	[thread overview]
Message-ID: <bug-67826-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67826
           Summary: gcc/fortran/openmp.c:1808: bad test ?
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

During a recent fortran build, I found

../../src/trunk/gcc/fortran/openmp.c:1808:33: warning: logical ‘and’ of
mutually exclusive tests is always false [-Wlogical-op]

Source code is

      && (ts->type == BT_DERIVED && ts->type == BT_CLASS)))

Maybe better code

      && (ts->type == BT_DERIVED || ts->type == BT_CLASS)))

I recommend an occasional fortran build with -Wlogical-op.
>From gcc-bugs-return-498657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Oct 02 20:33:48 2015
Return-Path: <gcc-bugs-return-498657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77511 invoked by alias); 2 Oct 2015 20:33:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77398 invoked by uid 48); 2 Oct 2015 20:33:45 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM
Date: Fri, 02 Oct 2015 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67756-4-hAUTAjTSqU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67756-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-SW-Source: 2015-10/txt/msg00212.txt.bz2
Content-length: 971

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

--- Comment #20 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Bernd Edlinger from comment #19)
> ok, but now we have because of the warnings:
> 
> FAIL: gcc.target/arm/pr67756.c (test for excess errors)
> 
> I think something like this could fix it:
> 
> Index: pr67756.c
> ===================================================================
> --- pr67756.c	(revision 228404)
> +++ pr67756.c	(working copy)
> @@ -2,6 +2,8 @@
>  /* { dg-require-effective-target arm_hard_vfp_ok } */
>  /* { dg-options "-O2 -mapcs -march=armv7-a -mfloat-abi=hard
> -mfpu=vfpv3-d16" } */
>  
> +int inode_permission (), try_break_deleg ();
> +int mutex_lock (), mutex_unlock ();
>  struct mutex
>  {
>  };

Thanks for checking.  Could you commit it.  Thanks.
>From gcc-bugs-return-498659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Oct 02 20:49:53 2015
Return-Path: <gcc-bugs-return-498659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17455 invoked by alias); 2 Oct 2015 20:49:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17271 invoked by uid 48); 2 Oct 2015 20:49:49 -0000
From: "jeromerobert at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/67308] FATAL: ThreadSanitizer: unexpected memory mapping
Date: Fri, 02 Oct 2015 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jeromerobert at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67308-4-VXjjfHi4RW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67308-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67308-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg00214.txt.bz2
Content-length: 275

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg308

--- Comment #3 from Jerome Robert <jeromerobert at gmx dot com> ---
It looks like PIE is no longer needed (at least with gcc 5.2).

echo 'void main(void){}' | gcc -fsanitize=thread -xc - -ltsan && ./a.out

just work fine.


             reply	other threads:[~2015-10-02 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 20:32 dcb314 at hotmail dot com [this message]
2015-10-08  9:12 ` [Bug fortran/67826] " dominiq at lps dot ens.fr

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-67826-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).