From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753603AbbCPKot (ORCPT ); Mon, 16 Mar 2015 06:44:49 -0400 Received: from edison.jonmasters.org ([173.255.233.168]:58555 "EHLO edison.jonmasters.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752676AbbCPKor (ORCPT ); Mon, 16 Mar 2015 06:44:47 -0400 X-Greylist: delayed 2581 seconds by postgrey-1.27 at vger.kernel.org; Mon, 16 Mar 2015 06:44:46 EDT Message-ID: <5506AA06.5070204@jonmasters.org> Date: Mon, 16 Mar 2015 06:01:42 -0400 From: Jon Masters User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: loody , Catalin Marinas CC: LKML References: <20150223132736.GH32737@e104818-lin.cambridge.arm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 74.92.29.237 X-SA-Exim-Mail-From: jonathan@jonmasters.org Subject: Re: some question about aarch32 for ARM64 X-SA-Exim-Version: 4.2.1 (built Sun, 08 Nov 2009 07:31:22 +0000) X-SA-Exim-Scanned: Yes (on edison.jonmasters.org) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.