From: Segher Boessenkool <segher@kernel.crashing.org>
To: unlvsur unlvsur <unlvsur@live.com>
Cc: Richard Sandiford <richard.sandiford@arm.com>,
unlvsur unlvsur via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Treat GCC cross compiler as a native compiler?
Date: Wed, 29 Jun 2022 11:59:39 -0500 [thread overview]
Message-ID: <20220629165939.GH25951@gate.crashing.org> (raw)
In-Reply-To: <DM6PR05MB46973C8BC3EFE166CE275932D6BB9@DM6PR05MB4697.namprd05.prod.outlook.com>
On Wed, Jun 29, 2022 at 03:15:27PM +0000, unlvsur unlvsur via Gcc-help wrote:
> “cross-native” toolchain should be called canadian toolchain.
build=host=target makes a "native compiler".
host=target otherwise is a "cross-built native compiler".
build=host otherwise is a "cross-compiler".
build=target otherwise is sometimes called a "cross-back compiler".
And all three of build, host, and target different is what is called a
"Canadian cross".
The main difficulty with doing cross-built native is that many checks
for native compilers only work on the systems themselves, and do not
usually have a convenient way to override that either. It's a fight
you cannot win, just build your native compilers on the system itself,
everyone else does!
Segher
next prev parent reply other threads:[~2022-06-29 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 3:53 unlvsur unlvsur
2022-06-29 7:44 ` Richard Sandiford
2022-06-29 15:15 ` unlvsur unlvsur
2022-06-29 16:59 ` Segher Boessenkool [this message]
2022-06-29 17:03 ` unlvsur unlvsur
2022-06-29 17:52 ` Segher Boessenkool
2022-06-29 17:58 ` unlvsur unlvsur
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=20220629165939.GH25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
--cc=unlvsur@live.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).