From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 840483858D33; Tue, 31 Jan 2023 18:24:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 840483858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675189482; bh=amfr8zeC3CKnbICQsl12hhMjmVHtwbZfubIPf5lHX6w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WKjIwkoO6LkX4Yrirgq9ySwZhUjINoRJsm1rJCWkER4ftx8Zid8aETbx1qQMxYnkO K/atQGYFalCsp1EbnBI8PZdBB8ikBQozlY1g/OhmgxC6+iRXAF2bHdjNd2v8lqfD9A A32GtAv7bvCpF9MLQ/1oo6UkQYRw712wycqo1Zgo= From: "rearnsha 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 18:24:42 +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: rearnsha 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 #19 from Richard Earnshaw --- (In reply to Andrew Pinski from comment #18) > I should say that testcase happens at `-Os -mstrict-align`, at `-O2 > -mstrict-align` it works. Because for -Os we don't forcibly align arrays - see=20 AARCH64_EXPAND_ALIGNMENT and the macros that use it.=