From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 672B23861823; Tue, 19 Dec 2023 12:58:59 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 672B23861823 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1702990739; bh=QOUpXqppZatq9PrSVqM/TMpEHfTRVAAjs8L77Bl2To0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=NRNJFPvsEKe05iuhavGeKS14WZ3Ynb256v9fWXnNmeMGBxGK5nK5IGLyz49DWru+T GW8fJVQ3SMJdY9SD6JYKOnA/kDP0ik+MDIuxiu/6Ly3v4c/THhX7jQWoEaMOBbS5kl gMo58OfD1cOiOcS8iExv9Ql42DDLYAyF0ZGl+haA= From: "mark 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: Tue, 19 Dec 2023 12:58:58 +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: mark 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: 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 --- Comment #17 from Mark Wielaard --- I am surprised valgrind memcheck doesn't produce more output, normally it w= ould tell you why & where it found the address invalid. I assume somehow valgrind memcheck believes it is reading past the end of a data buffer, while the co= de assumes this is fine because it will mask off the bits it won't use.=