From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23550 invoked by alias); 16 Nov 2012 15:35:19 -0000 Received: (qmail 23425 invoked by uid 22791); 16 Nov 2012 15:35:19 -0000 X-SWARE-Spam-Status: No, hits=-6.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-da0-f47.google.com (HELO mail-da0-f47.google.com) (209.85.210.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Nov 2012 15:35:13 +0000 Received: by mail-da0-f47.google.com with SMTP id s35so1135058dak.20 for ; Fri, 16 Nov 2012 07:35:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=WYbm1Gnd3mdIReY7LieU2j/qyQ0otYcLtmxl+6bLXBM=; b=hs+dvPt8am3tEoFO+nAiKFIhV9+p239J7BetPawjTCoffnmQPzPaVY6JA1JdakIaTR 6jEdp9L2VzzXmfBeDQxC5rQAIzJU5hU8Od3h2hzJtrUztJQrB7mIp8C0Wnwzn+zhAS9j AjeQ897pmwNnHj21HTSPy8s3gM2MDtXwNPt1JAyNP1nPwrkYO23VxuSKF2yQyAtw7TEX FoWz5P8KlPoNmtjYhxcAgF2TD+d9leLFWsjM3coSNMBiWcyVgrrI66/C6tRWNecvkp/8 HD1hVhGqT/lkaaIpOkR0vI/YhJV3tK4Q+IMeuVu877v+C8//uxNe9RdYB4k5hyxkA1hT NinA== MIME-Version: 1.0 Received: by 10.66.87.226 with SMTP id bb2mr13702694pab.57.1353080112568; Fri, 16 Nov 2012 07:35:12 -0800 (PST) Received: by 10.68.54.133 with HTTP; Fri, 16 Nov 2012 07:35:12 -0800 (PST) In-Reply-To: <50A60D68.5050100@redhat.com> References: <20121113.000747.810968224853699322.davem@davemloft.net> <3B06F4A9-2CC6-41F7-86D6-8B285833C81A@gmail.com> <50A3A160.4070608@arm.com> <50A60D68.5050100@redhat.com> Date: Fri, 16 Nov 2012 15:35:00 -0000 Message-ID: Subject: Re: ASAN merge... From: Ian Lance Taylor To: Andrew Haley Cc: Richard Earnshaw , Andrew Pinski , Ramana Radhakrishnan , Konstantin Serebryany , Diego Novillo , David Miller , "gcc-patches@gcc.gnu.org" , DodjiSeketeli Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkaXpY41P62N8HnFNG8oWlp5BJ5FoLVDBd34PGHHmpPyADdwZwcdfDRj8F+EZs/91iM8g9fzX5RFvtorYFziqLtRI1pGVCKdF20v3963HXffIaG8p7DVEjA4Ers9Iw97Iegx9A38Hr9KGMjZBolTZBhXMTVCmniMaVVS8GXj93yDN21V9JkI6TBH5mMv7qbNyeufOIt X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg01390.txt.bz2 On Fri, Nov 16, 2012 at 1:54 AM, Andrew Haley 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