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 072BA3858C35; Sun, 17 Dec 2023 20:11:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 072BA3858C35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1702843919;
	bh=gHoCRjFjbD98fUjJp8u42dFCdtxRzTscAb55uoAcDhA=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PQuGYnTY8sWutUdx4+wUuqYD+21a7COV1QhdlD5TA+koOxCfgVKvg+yZ45OH+eTg9
	 M0eGFt9qKYulfLstpSXhcKXaAua9Ncau/dcI70cqFhdXrz+MQrMhkhj7l/bYlUHd4k
	 TNM/tm48UYu5frI/fE1aIF5IEXKI/d4FCmjidF5s=
From: "pinskia 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: Sun, 17 Dec 2023 20:11: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: pinskia 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: bug_status everconfirmed cf_reconfirmed_on
Message-ID: <bug-113045-4-CcMK6ih4AO@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-12-17

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is almost definitely a valgrind issue.
We start with:
  /* Align the source pointer.  */
  misalign =3D (uintptr_t)s & 15;
  p =3D (const uint8_t *)((uintptr_t)s & -16);
  data =3D vld1q_u8 (p);


Which all other targets do too.

Basically this is how you realign the pointer and if don't depend on the by=
tes
that is not in the original pointer, then this is valid.

Does it work correctly without valgrind?=