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 4A83F3858298; Tue, 19 Dec 2023 09:22:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A83F3858298
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1702977744;
	bh=3IppeS5wEI2qlpmWQ6aXVehvkHOSsWRz/rWUC6BJ7fg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=k8uXhGzzvYh2XkOqZSU56ItGgpnn9Xh6SfDVkBOtotYgYEJs0cnArNg0DyRZWj6xG
	 w5LN7nS7ZBvp8SiH/AY8qWAUva6+9VLMIWnXGfRNc4icLheXYUCPa+rdRrbuT2Lg+b
	 7z6JMw84fBbAfDBQ+SNkdmiWxCh1C6xRJfJ2lKqs=
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: Tue, 19 Dec 2023 09:22:23 +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-P7S819wk0x@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 #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Not sheer fluke, it was the same ^d4ba3b369c commit both times, because that
was the oldest commit in your clone.=