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 15CB23858C98; Sun, 17 Dec 2023 18:21:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 15CB23858C98
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1702837313;
	bh=NtbSyHG68jwGT2wplNxdSlhgI65wTqqB/bfX8GZdEmY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UgS7SzANqJ/8uruGQ8mtOuvSEM7D4/qrWUxcHZO3+NPBhpTBPp6ugOC/2GNf0MSZD
	 Hy7I8tb2kFdmAeP+BFwF8Lb1fLtea3NoOpm7T/GRQvOWxI4op+Zljp0LVm6hJUeufN
	 zWJ62c2lKwONBROhMRrLMldLWbBhfmEpKD+/Bmhw=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113045] armv7l-unknown-linux-gnueabihf: valgrind error
 during build of libcc1
Date: Sun, 17 Dec 2023 18:21:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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-113045-4-qypAODvaDN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113045-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113045-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=3D113045

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's what the ^ on the commit suggests is happening.

You can fix your history with:
git fetch --unshallow=