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 0C83E3858C66; Fri, 22 Dec 2023 02:12:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C83E3858C66
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1703211179;
	bh=1MGVV5d37EK+QIDeQ0p+EhC/lbCKVovYwMsSpfg+qTk=;
	h=From:To:Subject:Date:From;
	b=wCUMLTN9qUchdDVVWAGMxiwYsyRcbkCHEJylNwb24QFYE4FIED8naJVx2f5KJoZAz
	 VgpLmbKPW1P8Z05ThU5b4Ew43auM6phrAYxhwxNrzsvCvMbEsfC6W97KtO2xSO5cuV
	 15u+OboGH32Sq7FUqFzzHqi1qeMu5m5iflXM/wuk=
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/113109] New: [14 Regression] g++ EH tests fail at
 execution time for cris-elf after r14-6674-g4759383245ac97
Date: Fri, 22 Dec 2023 02:12:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp 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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter cc target_milestone
 cf_gcchost cf_gcctarget
Message-ID: <bug-113109-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=3D113109

            Bug ID: 113109
           Summary: [14 Regression] g++ EH tests fail at execution time
                    for cris-elf after r14-6674-g4759383245ac97
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hp at gcc dot gnu.org
                CC: guojiufu at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: cris-elf

After r14-6674-g4759383245ac97, (at least) all tests that "throw", fail for
cris-elf at execution time: g++ tests as well as libstdc++ tests.  I don't =
see
any other clues from g++.log than execution failing for those tests.

Complete before/after example reports at
https://gcc.gnu.org/pipermail/gcc-testresults/2023-December/803815.html and
https://gcc.gnu.org/pipermail/gcc-testresults/2023-December/803816.html (for
r14-6672-g605d21f8ef1f and r14-6750-gf9be3d8faa47; same failures as 6674).

An example of a small hopefully-minimal test that fail is
gcc/testsuite/g++.old-deja/g++.mike/eh6.C.  Like for seemingly all others,
execution the test fails, and there's no output from the printf.  That
printf-statement is likely not reached, but the output *could* possibly sti=
ll
be in an output-buffer (I don't remember how that works in newlib; that cou=
ld
happen for glibc when execution is aborted).

I'm initially setting component to "middle-end" because that's what the com=
mit
touched and also, I'm biased, but visiting the gcc-testresults archives I d=
on't
see other targets fail in the same manner, so it could still be that "targe=
t"
fits better.  Further analysis will show; I'll dig a little deeper.  (Commit
author CC:ed.)=