From: Mathieu Malaterre <mathieu.malaterre@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: virtual memory exhausted: Cannot allocate memory
Date: Wed, 30 Nov 2022 08:19:41 +0100 [thread overview]
Message-ID: <CA+7wUsxJ4zHXFxbjvNZG7-YxBc3itGgHZX2Z9dhBBtbbzCv7vw@mail.gmail.com> (raw)
Hi all,
I am having a hard time understanding which flags to change in case of
`virtual memory exhausted: Cannot allocate memory`. I can compile
openvdb on all Debian supported arches but mipsel. I tried tweaking
the debug level as well as the optimization level without luck so far.
Latest attempt is:
g++-12 [...] -g0 -O0 --param ggc-min-expand=0 --param
ggc-min-heapsize=131072 [...]
What should I try next ?
Thanks much,
--
Mathieu
next reply other threads:[~2022-11-30 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 7:19 Mathieu Malaterre [this message]
2022-11-30 7:29 ` Florian Weimer
2022-12-01 7:42 ` Mathieu Malaterre
2022-12-01 12:30 ` Stefan Ring
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=CA+7wUsxJ4zHXFxbjvNZG7-YxBc3itGgHZX2Z9dhBBtbbzCv7vw@mail.gmail.com \
--to=mathieu.malaterre@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).