From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B8660385841E; Tue, 31 Jan 2023 17:51:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8660385841E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675187483; bh=4UY2xsUADHrc/qJH0By/CLTgT52D6tUapNoR+/wlK1E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hSGke5IQgvg2iPf3FU1AcYMJW3i7y7LCHd5Huf41W6f1zlg6QVXYRRHFok0+s+/PF iZJKmQgy+7S7Z+aEIBeE8q6AaYblW7P5lQZXhTFeQLn/pgPrMnY2odXe7stoq239E8 ARnikvWm1+ImN/gqFTa792zfGM4g2DBDRKs2BP0w= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103100] [11/12/13 Regression] unaligned access generated with memset or {} and -O2 -mstrict-align Date: Tue, 31 Jan 2023 17:51:23 +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: 11.2.0 X-Bugzilla-Keywords: patch, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: pinskia 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=3D103100 --- Comment #18 from Andrew Pinski --- (In reply to Andrew Pinski from comment #17) > Another testcase which is now affecting us at Marvell in our early firmwa= re: > ``` > void f(const char*); >=20 > void g(void) > { > char t[32] =3D "0l2345678"; > f(t); > } >=20 > ``` > So I am planning on getting back on this patch starting today. I should say that testcase happens at `-Os -mstrict-align`, at `-O2 -mstrict-align` it works.=