From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E18373858D1E; Sun, 9 Oct 2022 19:49:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E18373858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665344953; bh=tQ7Rgza1SQmy49n8sVUCuuMEOW79+y9USf8U+2403D0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=heHnXImIi4tENU6WR6fGCP7lxbxhfHtYUcMayEeS1tCYlqY67VZ+/ZoT9jbkTaGXQ P6UDxY4E9qc9pXW1gTRLMfCcARW+DVsqXb4TtzU7v4fkVTL6sqOsNRrwE2LH/mrjAI /BXltVim8iIjFsLpQ5eqzr6QZoBc75Q9KA/wApUI= From: "dcb314 at hotmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107197] valgrind error in function same_line_p during build Date: Sun, 09 Oct 2022 19:49:13 +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: 12.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: 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=3D107197 --- Comment #1 from David Binderman --- I can tell you that last weekend's valgrind build with -O2 went fine. That was from git hash ca01d2526917ec6e. This weekend's valgrind build, with -O3 enabled, is from git hash 6ffbf87ca66f4ed9cd79cff675fabe2109e46e85. So either someone has broken something this week in -O2, or -O3 has been broken for longer. I will take the -O3 off this weekend's build, drop back to -O2 and see what happens.=