From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4F3D3385DC14; Thu, 4 Jun 2020 17:24:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F3D3385DC14 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591291493; bh=Sws+RmvFIND6059ZLcLGlXpPbvGPUlExHMIwGDwnGY0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=xS0IjsTeEzQOsmDDvinpqPWe9sGjEGkkt8FHYC8vueLqKC4t3Z4ODSvNuk3QDu+Bx 7uIfxq+zdn6EIex7oPye0VUBZL64mKCmggL22TwNrei9qsuUv097/39wqalBhLNFBO JwmqyDHoxlYaF35aLGwO2OTbKwEs68NUbiC9RPB0= From: "anlauf at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95537] [11 regression] gfortran.dg/pr95090.f90 since r11-670 Date: Thu, 04 Jun 2020 17:24:53 +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: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: anlauf at gcc dot gnu.org 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: cc Message-ID: In-Reply-To: References: 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-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 17:24:53 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95537 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anlauf at gcc dot gnu.org --- Comment #2 from anlauf at gcc dot gnu.org --- It might be related. This testcase and the one in PR95530 exercise code paths with possibly latent bugs. Nevertheless, are you able to produce a traceback? valgrind on x86_64 unfortunately does not provide any useful hints.=