From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <richard.sandiford@arm.com>
Received: from foss.arm.com (foss.arm.com [217.140.110.172])
 by sourceware.org (Postfix) with ESMTP id 8B859385AE5D
 for <gcc-help@gcc.gnu.org>; Wed, 29 Jun 2022 07:44:40 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8B859385AE5D
Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14])
 by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 22A23152B;
 Wed, 29 Jun 2022 00:44:40 -0700 (PDT)
Received: from localhost (e121540-lin.manchester.arm.com [10.32.98.37])
 by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 63FB03F66F;
 Wed, 29 Jun 2022 00:44:39 -0700 (PDT)
From: Richard Sandiford <richard.sandiford@arm.com>
To: unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org>
Mail-Followup-To: unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org>,
 unlvsur unlvsur <unlvsur@live.com>, richard.sandiford@arm.com
Cc: unlvsur unlvsur <unlvsur@live.com>
Subject: Re: Treat GCC cross compiler as a native compiler?
References: <DM6PR05MB469797483A011E4E2B893045D6BB9@DM6PR05MB4697.namprd05.prod.outlook.com>
Date: Wed, 29 Jun 2022 08:44:38 +0100
In-Reply-To: <DM6PR05MB469797483A011E4E2B893045D6BB9@DM6PR05MB4697.namprd05.prod.outlook.com>
 (unlvsur unlvsur via Gcc-help's message of "Wed, 29 Jun 2022 03:53:46
 +0000")
Message-ID: <mptwnczvrq1.fsf@arm.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-50.3 required=5.0 tests=BAYES_00, KAM_DMARC_NONE,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: gcc-help@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-help mailing list <gcc-help.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-help>,
 <mailto:gcc-help-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2022 07:44:41 -0000

unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org> writes:
> I want to make =E2=80=93host=3Daarch64-linux-musl =E2=80=93target=3Daarch=
64-linux-android to be a native compiler instead of just a cross compiler f=
or aarch64-linux-android. Is that possible? (Since use aarch64-linux-androi=
d as host is difficult due to issues with -fPIC to stderr)

No, I don't think this is possible.  The usual definition of
"native compiler" is that the host and target are (exactly) the same.

It's possible (but difficult) to build a cross-native toolchain,
(build!=3Dhost, host=3D=3Dtarget).

Thanks,
Richard