From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: 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: Wed, 14 Nov 2012 01:03:00 -0000 [thread overview]
Message-ID: <CAJA7tRbNLuwKO4jtxoO6f5VPvTAN2fiyxELsOBorGY__L+J7xw@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1kPRu3-GpOztz6SVY0cZ=5kLz_VLd2yAUd9SADRdPEaTA@mail.gmail.com>
On Tue, Nov 13, 2012 at 10:41 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> On Tue, Nov 13, 2012 at 2:31 PM, Ramana Radhakrishnan
> <ramana.gcc@googlemail.com> wrote:
>>
>>
>> On 13 Nov 2012, at 21:18, Konstantin Serebryany <konstantin.s.serebryany@gmail.com> wrote:
>>
>>> On Tue, Nov 13, 2012 at 8:21 AM, Diego Novillo <dnovillo@google.com> wrote:
>>>> On Tue, Nov 13, 2012 at 12:07 AM, David Miller <davem@davemloft.net> wrote:
>>>>>
>>>>> This has broken the build on every Linux target that hasn't added
>>>>> the necessary cpu specific code to asan_linux.cc
>>>>
>>>> This should be fixed by Dodji's recent patch. ASAN is not currently
>>>> ported to any target other than x86/linux, so it should just be
>>>
>>> asan run-time (and the LLVM part) works on Mac and on ARM/Linux.
>>
>> And when you say ARM / Linux, has this been tested on older versions of the architecture or just v7-a ?
>
> And this arm is really arm32 and not ARM64 :).
Being an incorrigible pedant :)
Technically the 32 bit and the 64 bit execution states are AArch32 and
AArch64 as documented in the glossary on infocenter [1] . So if you
are inventing a term to distinguish between the two I would prefer
AArch32 rather than arm32 and arm64 because they don't come in any
documentation neither in the compiler source nor in the documentation
as it exists today - I do realize history and legacy have a part to
play but if you want a new term .....
Regards,
Ramana
1. http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.aeg0014e/ABCDEFGH.html
next prev parent reply other threads:[~2012-11-14 1:03 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 [this message]
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
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=CAJA7tRbNLuwKO4jtxoO6f5VPvTAN2fiyxELsOBorGY__L+J7xw@mail.gmail.com \
--to=ramana.gcc@googlemail.com \
--cc=davem@davemloft.net \
--cc=dnovillo@google.com \
--cc=dodji@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=konstantin.s.serebryany@gmail.com \
--cc=pinskia@gmail.com \
--cc=ramrad01@arm.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).