From: Adam Faiz via Guix-patches via <guix-patches@gnu.org>
To: Saku Laesvuori <saku@laesvuori.fi>
Cc: 65553@debbugs.gnu.org
Subject: [bug#65553] [PATCH 0/6] gnu: Add arrayfire.
Date: Mon, 28 Aug 2023 14:30:21 +0800 [thread overview]
Message-ID: <8b4252ad-63b5-df5b-623d-0c9df3a3b84e@disroot.org> (raw)
In-Reply-To: <20230826191856.lixehyli766k6oqm@X-kone>
On 8/27/23 03:18, Saku Laesvuori wrote:
> I have normally solve this by just adding a huge swapfile, but if
> someone knows how to actually reduce the ram usage by the linker that
> would be interesting to hear.
Thanks, using a swapfile worked for me.
The --no-keep-memory option reduces RAM usage for the linker, it was actually the compiler that was using up all my RAM.
To my understanding, the only effective way to reduce RAM usage of the compiler is to not have many running at the same time,
i.e. to reduce the number of parallel jobs by the build system.
The ggc-min-heapsize and ggc-min-expand GCC options could also be used instead, but I don't know if it's faster than just using swap.
Now I got ArrayFire to build, I just need to ensure its tests pass.
prev parent reply other threads:[~2023-08-28 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 18:46 [bug#65553] [PATCH 0/6] gnu: Add arrayfire Adam Faiz via Guix-patches via
2023-08-26 18:50 ` [bug#65553] [PATCH 1/6] gnu: Add arrayfire-glad Adam Faiz via Guix-patches via
2023-08-26 18:51 ` [bug#65553] [PATCH 2/6] gnu: Add span-lite Adam Faiz via Guix-patches via
2023-08-26 18:52 ` [bug#65553] [PATCH 3/6] gnu: Add arrayfire-threads Adam Faiz via Guix-patches via
2023-08-26 18:53 ` [bug#65553] [PATCH 4/6] gnu: Add arrayfire-forge Adam Faiz via Guix-patches via
2023-08-26 18:55 ` [bug#65553] [PATCH 5/6] gnu: Add arrayfire-docs Adam Faiz via Guix-patches via
2023-08-26 18:56 ` [bug#65553] [PATCH 6/6] gnu: Add arrayfire Adam Faiz via Guix-patches via
2023-08-26 19:18 ` [bug#65553] [PATCH 0/6] " Saku Laesvuori via Guix-patches via
2023-08-28 6:30 ` Adam Faiz via Guix-patches via [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b4252ad-63b5-df5b-623d-0c9df3a3b84e@disroot.org \
--to=guix-patches@gnu.org \
--cc=65553@debbugs.gnu.org \
--cc=adam.faiz@disroot.org \
--cc=saku@laesvuori.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).