From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 093323858D38; Mon, 23 Jan 2023 15:22:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 093323858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674487324; bh=8rPUeE0F1O8wuyTr80GDtBZSDPMNGGcOiqZk7mO62S4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HcVAFkuPiX0fNzDgnnFd9mWD6pi/ht/YTbMMW0RfuC1hMmcqrPfIDOoBV44JICHZl 8fbXyqmhJ7gVObkfWgm584JbcjweK1JCQHuRa6Gp2ssrygVsJp1IEhEPnnPX41v+Ca 9K//7IDnIpj1pqejpGntURw8ogR534WcIWwJMSfk= From: "kungfujesus06 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108498] ppc64 big endian generates uninitialized reads with -fstore-merging Date: Mon, 23 Jan 2023 15:22:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kungfujesus06 at gmail 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=3D108498 --- Comment #3 from Adam Stylinski --- (In reply to Andrew Pinski from comment #2) > This might be a valgrind bug of not tracking bits correctly for some ppc > instructions. It's most certainly not, though. That bit is explicitly being set to 0 fro= m an integer and with the optimization enabled it's printing 1.=