From: Sagar Acharya <sagaracharya@tutanota.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Cross Compiling for riscv64
Date: Tue, 14 Feb 2023 13:28:59 +0100 (CET) [thread overview]
Message-ID: <NOEtZxw--3-9@tutanota.com> (raw)
In-Reply-To: <8db704d6dae26764592f794835e07fc4100ed506.camel@xry111.site>
I'm compiling on RPI3.
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.
I thank you very much for your help, Xi!
Thanking you
Sagar Acharya
https://designman.org
14 Feb 2023, 17:18 by xry111@xry111.site:
> On Tue, 2023-02-14 at 12:37 +0100, Sagar Acharya via Gcc-help wrote:
>
>> g++: fatal error: Killed signal terminated program cc1plus
>> compilation terminated
>> make[2]: *** [Makefile:1143: gimple-match.o] Error 1
>>
>
> It looks like your system is out of memory then the kernel selects a
> process heavily using the memory and kill it. gimple-match.o is
> automatically generated, so it can be very large and compiling it will
> consume a large amount of memory.
>
> Try to add more RAM into your system, or build with a smaller -j value.
> The last resort is to add more swap space, but swapping can slow down
> the building process significantly.
>
> --
> Xi Ruoyao <xry111@xry111.site>
> School of Aerospace Science and Technology, Xidian University
>
next prev parent reply other threads:[~2023-02-14 12:29 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 [this message]
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
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=NOEtZxw--3-9@tutanota.com \
--to=sagaracharya@tutanota.com \
--cc=gcc-help@gcc.gnu.org \
--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).