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 55CD53858C50; Sun, 17 Dec 2023 21:05:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 55CD53858C50
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1702847101;
	bh=aPXQoSFLaZkGLVqodWgXTZc4HcCopxq9IewkuGtBA6s=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=gMpg4xTf47F2pkncLad/XIYnRoK5NzSVmu/+QCv8ZylTLSpcL5TSjy6XdKH58tN4K
	 Gt20OiWiPdQWa+PddEBKsSSMQW9i1mB2cgHRMHXJzAJqTj4upvwgN1bZbJ5kLvN7Sp
	 2fAc23UVu6xtjf+tA8UXuSk7HBa0oL1ALk6eWJTQ=
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 21:05:01 +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: 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: 
Message-ID: <bug-113045-4-J2YZ1315es@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 #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to David Binderman from comment #5)
> (In reply to Jonathan Wakely from comment #3)
> > I don't recognise that code, are you sure I wrote it?  d4ba3b369c did n=
ot
> > touch that code.
>=20
> No idea. git blame is known to lie from time to time. I am no
> expert at it.

It never lies. Here it's telling you the lines in question are present in t=
he
oldest commit in your repo. It's not git's fault that your history stops at
that commit.

You can use https://gcc.gnu.org/git or https://github.com/gcc-mirror/gcc to=
 see
the full history (and check blame for that file).=