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 636C83858C54; Wed, 30 Nov 2022 22:06:19 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 636C83858C54
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669845979;
	bh=4ffue+Sfhbl9ZvNuwkrzqloQ2uzkScCr2vXQTLmjt1Y=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=kRu/OtDwtF6d+t7q8ziqjDSiZCdUYPEHj2xaQuTMlhZOtC91QmnwFv/g94m6CjhpA
	 WDjIYWwQVB4qaaw4Bo7nylDfX7aJLMtvpG819qphZpP4UiJTJQ/aLZ+ahiH0Ql0DI5
	 8PbNZqvq/9bOyRImqPv4iOVuVMUk4iVwQExB9r6M=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107940] temp_directory_path testcase broken
Date: Wed, 30 Nov 2022 22:06:19 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: 
Message-ID: <bug-107940-4-x3gWLvN9xc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107940-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107940-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=3D107940

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to laurent.alfonsi@linaro.org from comment #0)
> > This may be linked to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D90=
787.
> > But, I confirm my toolchain is based on trunk (13.0), and contains the =
90787
> > fix.
>=20
> No, I don't think it's related to that in any way.
>=20
> valgrind and asan are both clean when running that test on
> x86_64-pc-linux-gnu.
>=20
> Where does valgrind say there are uninitialized values? Maybe the problem=
 is
> in the unwinder.

I suspect the problem is the unwinder which is why I put PR 107678 and PR
107675 as see also bug reports. Both are those are aarch64 specific issues
relating to unwind issues against the trunk. This might be the same issue t=
here
too.=