From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 265C13858D33; Tue, 24 Jan 2023 16:48:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 265C13858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674578911; bh=D7SUpm9VjGcaQSCYZQ4LbpvWre2my6Jxr9ukZO4pvpk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=TZ6pZ1SGE2MW45IogH6oGGl+hKafvoKFKJadQJ9l/p8Uxf+17yEReF305mq0CyTnv X5TM2j3rM90XVsq1lFswWlniDJ8gCHceaz70wYDWpzVp0BE1ZK+nuPAexDIN5QdeYb y51fN/0nyBOQYIBijg+KsM/I4941IGmxo6tWHsF4= From: "ebotcazou at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108498] [11/12/13 Regression] ppc64 big endian generates uninitialized reads with -fstore-merging Date: Tue, 24 Jan 2023 16:48:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ebotcazou at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.4 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 #21 from Eric Botcazou --- > That said, I think especially for backports to 11/12 and perhaps even for= 13 > the easiest will be the second option, clear string_merging on non-aligned > start/width. >=20 > Eric, your thoughts on this? Yes, nonaligned strings do not make much sense. Where do they come from in your first testcase? Is it fold-const synthesizing STRING_CST from INTEGER_CST?=