public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kyrylo Tkachov <ktkachov@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6320] aarch64: Update FLAGS field documentation comment in aarch64-cores.def Date: Fri, 24 Feb 2023 11:41:58 +0000 (GMT) [thread overview] Message-ID: <20230224114158.8E94F385840F@sourceware.org> (raw) https://gcc.gnu.org/g:b580721f034957f314fccf99ccc772c41b735039 commit r13-6320-gb580721f034957f314fccf99ccc772c41b735039 Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com> Date: Fri Feb 24 11:41:28 2023 +0000 aarch64: Update FLAGS field documentation comment in aarch64-cores.def With the cleanup of the arch features in GCC 13 the comment on the FLAGS field in aarch64-cores.def is now outdated. It's now a comma-separated list rather than a bitwise or. Spotted while reviewing an aarch64-cores.def patch. Update the comment. gcc/ChangeLog: * config/aarch64/aarch64-cores.def (FLAGS): Update comment. Diff: --- gcc/config/aarch64/aarch64-cores.def | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/gcc/config/aarch64/aarch64-cores.def b/gcc/config/aarch64/aarch64-cores.def index 85fdfd8bf74..2ec88c98400 100644 --- a/gcc/config/aarch64/aarch64-cores.def +++ b/gcc/config/aarch64/aarch64-cores.def @@ -29,7 +29,10 @@ will be made, represented as an identifier. ARCH_IDENT is the architecture implemented by the chip as specified in aarch64-arches.def. - FLAGS are the bitwise-or of the traits that apply to that core. + FLAGS is a parentheses-enclosed, comma-separated list of architecture + features in the core that are present in addition to the base architecture. + The architecture feature names are as per the identifiers in + aarch64-option-extensions.def. This need not include flags implied by the architecture. COSTS is the name of the rtx_costs routine to use. IMP is the implementer ID of the CPU vendor. On a GNU/Linux system it
reply other threads:[~2023-02-24 11:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230224114158.8E94F385840F@sourceware.org \ --to=ktkachov@gcc.gnu.org \ --cc=gcc-cvs@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).