From: Xi Ruoyao <xry111@xry111.site>
To: Sagar Acharya <sagaracharya@tutanota.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross Compiling for riscv64
Date: Tue, 14 Feb 2023 20:43:18 +0800 [thread overview]
Message-ID: <4db1fdb33d0f4006e0b083b4429949337a740c01.camel@xry111.site> (raw)
In-Reply-To: <NOEtZxw--3-9@tutanota.com>
On Tue, 2023-02-14 at 13:28 +0100, Sagar Acharya wrote:
> The real question is, whether building a compiler should require 900MB
> memory?
>
> And my answer to it is a clear undisputed no. 900MB is more than
> enough memory for building a compiler.
GCC is a real compiler, not an example in the compiler textbook.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-02-14 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 11:37 Sagar Acharya
2023-02-14 11:48 ` Xi Ruoyao
2023-02-14 12:28 ` Sagar Acharya
2023-02-14 12:43 ` Xi Ruoyao [this message]
2023-02-14 12:57 ` Sagar Acharya
2023-02-14 13:02 ` Xi Ruoyao
2023-02-14 13:27 ` Jonathan Wakely
2023-02-14 13:36 ` Kai Ruottu
2023-02-14 13:46 ` Kai Ruottu
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=4db1fdb33d0f4006e0b083b4429949337a740c01.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-help@gcc.gnu.org \
--cc=sagaracharya@tutanota.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).