public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "syq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111555] [AArch64] __ARM_FEATURE_UNALIGNED should be undefined with -mstrict-align Date: Thu, 14 Mar 2024 23:37:56 +0000 [thread overview] Message-ID: <bug-111555-4-eMJ4quhiUi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111555-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111555 YunQiang Su <syq at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |syq at gcc dot gnu.org --- Comment #2 from YunQiang Su <syq at gcc dot gnu.org> --- `-mno-unaligned-access` is also supported by MIPSr6. I guess we should add a more generic macro for this case? Is __UNALIGN_ACCESS_DISABLED__ OK? For AArch64, clang supports `-mno-unaligned-access`, while gcc doesn't, should we add it as an alias of -mstrict-align?
next prev parent reply other threads:[~2024-03-14 23:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-23 17:42 [Bug target/111555] New: " lasse.collin at tukaani dot org 2023-09-23 17:47 ` [Bug target/111555] " pinskia at gcc dot gnu.org 2024-03-14 23:37 ` syq at gcc dot gnu.org [this message] 2024-03-14 23:45 ` pinskia at gcc dot gnu.org 2024-03-14 23:46 ` pinskia at gcc dot gnu.org 2024-03-15 2:20 ` i at maskray dot me
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-111555-4-eMJ4quhiUi@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).