From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Sagar Acharya <sagaracharya@tutanota.com>
Cc: Xi Ruoyao <xry111@xry111.site>, gcc-help@gcc.gnu.org
Subject: Re: Cross Compiling for riscv64
Date: Tue, 14 Feb 2023 13:27:52 +0000 [thread overview]
Message-ID: <CAH6eHdRHLbYBT9HPh3e65vFc+SrxrkjLi7kzO_RKuDXJ9kizKA@mail.gmail.com> (raw)
In-Reply-To: <NOF-04_--3-9@tutanota.com>
On Tue, 14 Feb 2023 at 12:58, Sagar Acharya via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Point of a compiler is to convert C code to machine code of hex/binary/object file
Correct so far.
> in least amount of time and conserving as much memory as can be done.
No, that is a nice-to-have feature, not "the point of a compiler".
> To create good error-free sequence of instructions is also one objective.
Yes.
> The values of memory required are definitely not of order 1GB. There are OSes which can be booted in less than 100MB.
Have you actually looked at what is being compiled for gimple-match.o?
It's meaningless to compare it to booting an OS, those are two
completely different things.
You could try compiling that file without optimization, or you could
try building the compiler on a machine with more memory then copying
it to your rpi.
next prev parent reply other threads:[~2023-02-14 13:28 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
2023-02-14 12:57 ` Sagar Acharya
2023-02-14 13:02 ` Xi Ruoyao
2023-02-14 13:27 ` Jonathan Wakely [this message]
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=CAH6eHdRHLbYBT9HPh3e65vFc+SrxrkjLi7kzO_RKuDXJ9kizKA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=sagaracharya@tutanota.com \
--cc=xry111@xry111.site \
/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).