From: David Starner <prosfilaes@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: [Request for Comments] Using Rust libraries in the Rust frontend
Date: Fri, 26 Jan 2024 17:25:45 -0600 [thread overview]
Message-ID: <CAMZ=zj60yc_DiE-64wUhFEgxEbD5e2sz_vUxm1LKu+m682p=Mw@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLtNSJN1CQ2G79XQBcEe2BcAn-bk1H=19MwPZkDr7uRnoQ@mail.gmail.com>
On Fri, Jan 26, 2024 at 3:40 PM NightStrike via Gcc <gcc@gcc.gnu.org> wrote:
>
> On Thu, Jan 25, 2024, 11:27 Iain Sandoe <iain@sandoe.co.uk> wrote:
>
> > E.g. with Ada it is possible to port to a new platform by first building a
> > cross-compiler and then to use that cross-compiler to build a “native
> > cross” (build != host == target) to provide an initial compiler on the
> > target platform.
> >
>
> And that Ada solution is awful for nontraditional systems. Ditto for D.
Why? And what solution would you suggest for compilers written in part
in their own languages? How do you get the first C compiler on the
platform without building a cross-compiler?
--
The standard is written in English . If you have trouble understanding
a particular section, read it again and again and again . . . Sit up
straight. Eat your vegetables. Do not mumble. -- _Pascal_, ISO 7185
(1991)
next prev parent reply other threads:[~2024-01-26 23:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:30 Arthur Cohen
2024-01-23 7:23 ` Richard Biener
2024-01-25 15:03 ` Arthur Cohen
2024-01-25 15:55 ` connor horman
2024-01-26 9:30 ` Arthur Cohen
2024-01-25 16:26 ` Iain Sandoe
2024-01-26 9:28 ` Arthur Cohen
2024-01-26 21:39 ` NightStrike
2024-01-26 23:25 ` David Starner [this message]
2024-01-25 18:19 ` Richard Biener
2024-01-26 9:24 ` Arthur Cohen
2024-01-26 21:41 ` NightStrike
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='CAMZ=zj60yc_DiE-64wUhFEgxEbD5e2sz_vUxm1LKu+m682p=Mw@mail.gmail.com' \
--to=prosfilaes@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=nightstrike@gmail.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).