LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: loody <miloody@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: some question about aarch32 for ARM64
Date: Tue, 24 Feb 2015 13:19:30 +0800	[thread overview]
Message-ID: <CANudz+ujtoK6vD+O2z6fTHGK5aLeWdX4u1fD8-i59y8ZP0wBZA@mail.gmail.com> (raw)
In-Reply-To: <20150223132736.GH32737@e104818-lin.cambridge.arm.com>

hi catalin:

2015-02-23 21:27 GMT+08:00 Catalin Marinas <catalin.marinas@arm.com>:
> On Mon, Feb 23, 2015 at 12:28:57PM +0000, loody wrote:
>> I follow below instructions to compile a simple c file as aarch32 but in vain.
>>
>> https://gcc.gnu.org/onlinedocs/gcc-4.9.1/gcc/AArch64-Options.html#AArch64-Options
>
> On the above link, there are no instructions on how to compile an
> AArch32 application with the AArch64 compiler. You need an AArch32 gcc
> (e.g. arm-linux-gnu-gcc, not aarch64-linux-gnu-gcc).
>
>> I saw there are aarch32 support in arm64 kernel porting.
>
> Yes, that's to support AArch32 binaries (ARMv8/v7/...).
>
>> Would you mind to let us know how to get aarch32 ELF for running on
>> ARM64 processors?
>
> Just use the right compiler.
>
>> 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 ^^

  reply	other threads:[~2015-02-24  5:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 12:28 loody
2015-02-23 13:27 ` Catalin Marinas
2015-02-24  5:19   ` loody [this message]
2015-03-16 10:01     ` Jon Masters

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=CANudz+ujtoK6vD+O2z6fTHGK5aLeWdX4u1fD8-i59y8ZP0wBZA@mail.gmail.com \
    --to=miloody@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: some question about aarch32 for ARM64' \
    /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

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).