From: YunQiang Su <syq@gcc.gnu.org>
To: Sam James <sam@gentoo.org>
Cc: gcc-patches@gcc.gnu.org, pinskia@gcc.gnu.org, i@maskray.me,
rguenther@suse.de
Subject: Re: [PATCH] Predefine __STRICT_ALIGN__ if STRICT_ALIGNMENT
Date: Sun, 17 Mar 2024 15:27:37 +0800 [thread overview]
Message-ID: <CAKcpw6U0FDD__gQ4836GOLCNvvBeJkA6Bdb7Het0Dj19+mq0HA@mail.gmail.com> (raw)
In-Reply-To: <87v85lxukr.fsf@gentoo.org>
Sam James <sam@gentoo.org> 于2024年3月17日周日 14:04写道：
>
> YunQiang Su <syq@gcc.gnu.org> writes:
>
> > Arm32 predefines __ARM_FEATURE_UNALIGNED if -mno-unaligned-access,
> > and RISC-V predefines __riscv_misaligned_avoid, while other ports
> > that support -mstrict-align/-mno-unaligned-access don't have such
> > macro, and these backend macros are only avaiable for c-family.
> > Note: Arm64 always predefine __ARM_FEATURE_UNALIGNED: See #111555.
>
> I would say tag the bug even if you're not fixing it, as it was related
> enough for you to cite it.
>
I am not sure that it is a bug for aarch64. This macro may be used to
determine whether hardware can support misaligned access, and
maybe all of Aarch64 CPUs can support it.
It should be determined by ARM people.
next prev parent reply other threads:[~2024-03-17 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 5:46 YunQiang Su
2024-03-17 6:04 ` Sam James
2024-03-17 7:27 ` YunQiang Su [this message]
2024-03-18 7:32 ` Richard Biener
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=CAKcpw6U0FDD__gQ4836GOLCNvvBeJkA6Bdb7Het0Dj19+mq0HA@mail.gmail.com \
--to=syq@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=i@maskray.me \
--cc=pinskia@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=sam@gentoo.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: link
Be 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).