From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jackson Pfeffer <crazykidjack@gmail.com>
Cc: Chengyin Yao <chengyin.yao@live.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How to move gcc to compile to my own architecture?
Date: Fri, 16 Sep 2022 21:09:20 +0100 [thread overview]
Message-ID: <CAH6eHdQ3NVZeXyYyM0SqVgLg=UfMea-0L1vBVjKy-zT+thNGvQ@mail.gmail.com> (raw)
In-Reply-To: <CAE539w-PfeyeqKuBhTcrS3=tSwydNmtbcvLW7tt0VmUNPAm2bQ@mail.gmail.com>
On Fri, 16 Sept 2022 at 20:51, Jackson Pfeffer <crazykidjack@gmail.com> wrote:
>
> I shouldn't assume (you know what happens)... But I assume they are asking how to compile GCC from source on a machine running (for example) some ARM chip running Linux to get an executable GCC that will run on (for example) an Intel x64 chip running windows.
>
> I assume (there it is again) that they are compiling on one well known "architecture" targeting another well known (but different) "architecture".
>
> I'm a GCC noob, but I think this basically amounts to them needing a cross compiler.
Indeed, I should have said that the fist link on the osdev wiki covers
that case (which is much simpler than porting GCC to a brand new
architecture).
See https://wiki.osdev.org/GCC_Cross-Compiler for cross compiler
details. That's all you need to be able to use one type of machine to
compile code for a different type of machine.
prev parent reply other threads:[~2022-09-16 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 16:03 Chengyin Yao
2022-09-16 16:27 ` Jonathan Wakely
2022-09-16 19:50 ` Jackson Pfeffer
2022-09-16 20:09 ` Jonathan Wakely [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='CAH6eHdQ3NVZeXyYyM0SqVgLg=UfMea-0L1vBVjKy-zT+thNGvQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=chengyin.yao@live.com \
--cc=crazykidjack@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).