From: Jon Masters <jonathan@jonmasters.org>
To: loody <miloody@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: some question about aarch32 for ARM64
Date: Mon, 16 Mar 2015 06:01:42 -0400 [thread overview]
Message-ID: <5506AA06.5070204@jonmasters.org> (raw)
In-Reply-To: <CANudz+ujtoK6vD+O2z6fTHGK5aLeWdX4u1fD8-i59y8ZP0wBZA@mail.gmail.com>
On 2/24/15, 12:19 AM, loody wrote:
>>> PS:Below is my compile error message:
>>> #aarch64-linux-gnu-gcc -mabi=ilp32 test.c
>>
>> -mabi=ilp32 is entirely different from an AArch32 compiler. The above
>> still generates AArch64 but with the ILP32 ABI (sizeof int/long/pointer
>> is 32-bit).
> so per your explanation, AArch32 binary could be created by any
> arm-linux-gnu-gcc which support armv7 and previous instructions.
> And -mabi=ilp32 is still aarch64 but with ILP32 ABI.
> appreciate your kind help ^^
This is the correct summary.
Jon.
prev parent reply other threads:[~2015-03-16 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:28 some question about aarch32 for ARM64 loody
2015-02-23 13:27 ` Catalin Marinas
2015-02-24 5:19 ` loody
2015-03-16 10:01 ` Jon Masters [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=5506AA06.5070204@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miloody@gmail.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 NNTP newsgroup(s).