public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "userm57 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109927] Bootstrap fails for m68k in stage2 compilation of gimple-match.cc
Date: Tue, 23 May 2023 17:28:37 +0000 [thread overview]
Message-ID: <bug-109927-4-RnpGGEr4sn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109927-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #10 from Stan Johnson <userm57 at yahoo dot com> ---
> The question is how much virtual memory is exposed to a user
> process, that is - how large is the address space?
I'm not sure, but I see this:
$ prlimit
RESOURCE DESCRIPTION SOFT HARD UNITS
AS address space limit unlimited unlimited bytes
CORE max core file size 0 unlimited bytes
CPU CPU time unlimited unlimited seconds
DATA max data size unlimited unlimited bytes
FSIZE max file size unlimited unlimited bytes
LOCKS max number of file locks held unlimited unlimited locks
MEMLOCK max locked-in-memory address space 8388608 8388608 bytes
MSGQUEUE max bytes in POSIX mqueues 819200 819200 bytes
NICE max nice prio allowed to raise 0 0
NOFILE max number of open files 1024 4096 files
NPROC max number of processes 26236 26236 processes
RSS max resident set size unlimited unlimited bytes
RTPRIO max real-time priority 0 0
RTTIME timeout for real-time tasks unlimited unlimited microsecs
SIGPENDING max number of pending signals 26236 26236 signals
STACK max stack size 8388608 unlimited bytes
As long as those are also the limits for portage, it should be ok.
> Note mainline would be gcc 14.0, you can probably download a recent
> snapshot.
ok, I've downloaded the latest gcc snapshot using git. I'll try a manual
bootstrap of that. Do you recommend that I use QEMU m68k (virt) running Debian
SID or Gentoo, or doesn't it matter?
next prev parent reply other threads:[~2023-05-23 17:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 1:32 [Bug bootstrap/109927] New: " userm57 at yahoo dot com
2023-05-22 3:04 ` [Bug target/109927] " pinskia at gcc dot gnu.org
2023-05-22 6:25 ` xry111 at gcc dot gnu.org
2023-05-22 8:23 ` rguenth at gcc dot gnu.org
2023-05-23 0:09 ` userm57 at yahoo dot com
2023-05-23 5:32 ` sjames at gcc dot gnu.org
2023-05-23 15:00 ` userm57 at yahoo dot com
2023-05-23 15:29 ` rguenth at gcc dot gnu.org
2023-05-23 16:18 ` userm57 at yahoo dot com
2023-05-23 16:58 ` rguenther at suse dot de
2023-05-23 17:28 ` userm57 at yahoo dot com [this message]
2023-05-23 17:35 ` rguenther at suse dot de
2023-05-23 17:44 ` userm57 at yahoo dot com
2023-05-23 18:24 ` rguenther at suse dot de
2023-05-23 18:42 ` userm57 at yahoo dot com
2023-05-23 19:04 ` schwab@linux-m68k.org
2023-05-24 6:54 ` rguenth at gcc dot gnu.org
2023-05-24 7:59 ` schwab@linux-m68k.org
2023-05-24 23:19 ` userm57 at yahoo dot com
2023-05-25 7:24 ` rguenther at suse dot de
2023-05-25 7:41 ` sjames at gcc dot gnu.org
2023-05-25 7:47 ` rguenther at suse dot de
2023-07-27 9:48 ` sjames at gcc dot gnu.org
2023-07-28 7:50 ` rguenth at gcc dot gnu.org
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=bug-109927-4-RnpGGEr4sn@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).