From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 5D0033858C41; Wed, 17 May 2023 03:08:16 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D0033858C41
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1684292896;
	bh=ePwP9/VRQgXwcDTqaqjqftCq7M7KG9Rruwc0LnldHFk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=nFmQ5kSu1zrYnYMTGfjaAvqkhB5EAFuyzaD0UEoR1GkK/P9/0LDgBoi9pd3WUYNzF
	 HD/qetIeY+byLiYiQ20+E8ddHG6Yq/9pusktGyBusN8322nudLq3ei7zDX45QmSkSa
	 f4b10S5uR5mN8BqQp1PLRanQgR4QbHYK4w9lvJGk=
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/109865] different results when routine moved inside the
 contains statement
Date: Wed, 17 May 2023 03:08:15 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: og12 (devel/omp/gcc-12)
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: cc
Message-ID: <bug-109865-4-dbVYGiPUaS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109865-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
List-Id: <gcc-bugs.sourceware.org>

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

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.o=
rg

--- Comment #15 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to GARY.WHITE@ColoState.edu from comment #11)
> I've never used valgrind -- what would it do?
>=20
 valgrind tracks and checks memory allocations during execution and can spot
where things, such as pointers that go astray.  This sometimes happens with
optimization bugs.

>From the man page. It has many tools and is very useful.

       Valgrind is a flexible program for debugging and profiling Linux
       executables. It consists of a core, which provides a synthetic CPU in
       software, and a series of debugging and profiling tools. The
       architecture is modular, so that new tools can be created easily and
       without disturbing the existing structure.=