public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
	gcc-patches@gcc.gnu.org,
	 Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Arm branding (was: [PATCH] doc: Document arm_v8_1m_main_cde_mve_fp)
Date: Tue, 28 May 2024 13:31:41 +0400 (+04)	[thread overview]
Message-ID: <44a0308a-a960-7f10-cbe1-369e0c6e4e18@pfeifer.com> (raw)
In-Reply-To: <PAXPR08MB6926E6FFB94EB61012AA898E9330A@PAXPR08MB6926.eurprd08.prod.outlook.com>

On Mon, 10 Jul 2023, Kyrylo Tkachov via Gcc-patches wrote:
> I know the GCC source is inconsistent on this but the proper branding 
> these days is "ARM" -> "Arm" and "ARMv8.1-M" -> "Armv8.1-M".

Arm, Red Hat, and SUSE - those three are spelt incorrectly by third 
parties more often than not, it seems. :-(

Is it always Arm now in every context and meaning (outside target 
triplets)?

If so, I'll add a line to our table in codingconventions.html?
If not, can you explain the specifics?

Gerald

      reply	other threads:[~2024-05-28  9:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  7:51 [PATCH] doc: Document arm_v8_1m_main_cde_mve_fp Christophe Lyon
2023-07-07  7:51 ` [PATCH] testsuite: Add _link flavor for several arm_arch* and arm* effective-targets Christophe Lyon
2023-07-10 13:45   ` Kyrylo Tkachov
2023-07-10 13:58     ` Christophe Lyon
2023-07-10 14:02       ` Kyrylo Tkachov
2023-07-10 13:47 ` [PATCH] doc: Document arm_v8_1m_main_cde_mve_fp Kyrylo Tkachov
2024-05-28  9:31   ` Gerald Pfeifer [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=44a0308a-a960-7f10-cbe1-369e0c6e4e18@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=Kyrylo.Tkachov@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=christophe.lyon@linaro.org \
    --cc=gcc-patches@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: 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).