From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7AD8C385828B; Mon, 18 Dec 2023 08:18:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7AD8C385828B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1702887510; bh=ssLwXMZlQq/+woFIvv4jGoHWOqaRc6JO0t2h1kMQWFE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QnemYT+vLBOoe88C3YbIyx6f1EsY2/neY0TYqJV/3+IHkNw5/0eIMSX/0W+QW3oS1 JOLxWU+OlO42xcniuwDL+aLRGDu3sciumauzBjiKByPqQB8dW5vsrhNSCF0ySec9XD ELZrp6QHwqTm9CfDDJ/rXbhtZ2iotpXT7prmom0Y= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113045] armv7l-unknown-linux-gnueabihf: valgrind error during build of libcc1 Date: Mon, 18 Dec 2023 08:18:27 +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: rguenth 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: cf_gcctarget Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113045 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |arm --- Comment #13 from Richard Biener --- Yeah, I think that's an artifact of using valgrind. But I can't see how valgrind could be fixed here apart from trying to special-case a bigger instruction pattern.=