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 AC3183986416; Thu, 17 Nov 2022 11:47:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AC3183986416
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668685672;
	bh=GMKecHgX5YCek67fJs5mlMEBwWWlLzDvQQlaeuIeCcs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=qO/9pP7Rvyd6WcQafE4Jc8HHjkEfomaIaQJTz2bef8r7SWgsOF4HbcaUURcIFFwG4
	 Sx1vN8KaYR2X4Y/lzqqeX6cyIra3S3y0D4may8PszlwfP2jw5kP4V1Ak7DOpAam4L5
	 TPI1l4r1PKc17CNudfQ0xY+Nn6K0AY0oSCk1LVis=
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107734] valgrind error for
 gcc/testsuite/cc.target/i386/pr46051.c
Date: Thu, 17 Nov 2022 11:47:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
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-107734-4-evWJDeyPNz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107734-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=3D107734

--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
The valgrind problem doesn't seem to occur with git hash 05432288d4e56055,
dated 20221113, so the bug is recent.

I used git hash 2b2f2ee49a33419f for today's build.=