public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108943] ARM Unaligned memory access with high optimizer levels Date: Mon, 27 Feb 2023 13:12:53 +0000 [thread overview] Message-ID: <bug-108943-4-riIIPljZHi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108943-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108943 Richard Earnshaw <rearnsha at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- There's no compiler bug here. Cortex-M7 implements the ARMv7em version of the architecture, which supports unaligned accesses. If this is faulting then it's because you're trying to use the operation on something like device memory without informing the compiler about this. You need to mark your pointers as volatile in this case. The alternative is to compile with -mno-unaligned-access, but I wouldn't recommend this as that will disable other optimizations where this might be safe and useful.
prev parent reply other threads:[~2023-02-27 13:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 10:35 [Bug c/108943] New: " gcc@dynamic-noise.net 2023-02-27 13:12 ` rearnsha at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-108943-4-riIIPljZHi@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).