From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 65BD03858D3C; Mon, 23 Jan 2023 15:34:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 65BD03858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674488047; bh=czl1LFeTZeoX9f4Q/S0GizabTYLZkN1LGIkj/i0nuAI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Nw25znW64MVWCY/wcn10c92ZDuK7b2d1hVcCjZJFK8j+CE/Yn/5H52+DZ0YArYNMP pFPxx8R0E+0DUPF2SeARS4lZQRP0lu4QufqqgO3lXx/mLxmcia3yBx/r9OQws+Kg7d ZaCSLomEEl63MBl2FZJz4Ls6/OsGWe9YkReR7c00= 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:34:07 +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 #4 from Adam Stylinski --- Also I strongly suspect valgrind is correctly identifying the unitialized b= its because the underlying bug it produces is a "sometimes" bug, depending on what's on the heap. Sometimes insn.sat is 0 (when it behaves correctly), sometimes it's 1 (black screen).=