From: Richard Earnshaw <rearnsha@arm.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "aph@redhat.com" <aph@redhat.com>,
Andrew Pinski <pinskia@gmail.com>,
Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
Konstantin Serebryany <konstantin.s.serebryany@gmail.com>,
Diego Novillo <dnovillo@google.com>,
David Miller <davem@davemloft.net>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
DodjiSeketeli <dodji@redhat.com>
Subject: Re: ASAN merge...
Date: Fri, 16 Nov 2012 15:43:00 -0000 [thread overview]
Message-ID: <50A65F21.7010504@arm.com> (raw)
In-Reply-To: <CAKOQZ8y-byoFE8at0DW-ZMKbOA-Dd+BxOLn5Ar+wivVH4H7bRA@mail.gmail.com>
On 16/11/12 15:35, Ian Lance Taylor wrote:
> On Fri, Nov 16, 2012 at 1:54 AM, Andrew Haley <aph@redhat.com> wrote:
>> On 11/14/2012 01:49 PM, Richard Earnshaw wrote:
>>
>>> Please please don't get into the habit of calling it ARM32 and ARM64,
>>> you're just sowing confusion; there are good reasons why those names
>>> weren't adopted (some technical, some not) and I'm not about to rehash
>>> them all now. AArch32 and AArch64 aren't that much harder to type and
>>> they are completely unambiguous.
>>
>> And they can't be pronounced in any reasonable way. I think
>> you're going to lose this one.
>
> I expect it's pronounced with a sort of throat-clearing noise that is
> hard to write. Sort of like the gargling sound represented by "argh."
> argh32 and argh64.
>
> Ian
>
No, its pronounced Ay-Arch. It's not really hard to say, or think.
R.
next prev parent reply other threads:[~2012-11-16 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 5:07 David Miller
2012-11-13 16:22 ` Diego Novillo
2012-11-13 16:52 ` H.J. Lu
2012-11-13 18:46 ` David Miller
2012-11-14 13:26 ` Dodji Seketeli
2012-11-14 17:06 ` David Miller
2012-11-13 21:19 ` Konstantin Serebryany
2012-11-13 22:31 ` Ramana Radhakrishnan
2012-11-13 22:41 ` Andrew Pinski
2012-11-13 23:19 ` Konstantin Serebryany
2012-11-14 1:03 ` Ramana Radhakrishnan
2012-11-14 13:49 ` Richard Earnshaw
2012-11-16 9:55 ` Andrew Haley
2012-11-16 15:35 ` Ian Lance Taylor
2012-11-16 15:43 ` Richard Earnshaw [this message]
2012-11-17 19:20 ` Toon Moene
2012-11-14 11:51 ` Dodji Seketeli
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=50A65F21.7010504@arm.com \
--to=rearnsha@arm.com \
--cc=aph@redhat.com \
--cc=davem@davemloft.net \
--cc=dnovillo@google.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=konstantin.s.serebryany@gmail.com \
--cc=pinskia@gmail.com \
--cc=ramana.gcc@googlemail.com \
/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).