https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #18 from Stan Johnson ---
$ git clone git://gcc.gnu.org/git/gcc.git
$ cd gcc
$ git checkout master
I'm testing a manual bootstrap of "gcc version 14.0.0 20230524 (experimental)
(GCC)" now, accessed via git as shown above.
It will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #14 from Stan Johnson ---
I can try to capture the offending "cc1plus" and "as" processes just before the
compilation of gimple-match.cc fails in stage2; the output will look something
like this (for a different cc1plus process
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #10 from Stan Johnson ---
> 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #8 from Stan Johnson ---
> How much virtual memory does the m68k host have?
Swap space in the m68k virt VM is configurable; I'm using 1 GiB in two 512 MiB
partitions. I noticed that compilation goes further with two 512 MiB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #6 from Stan Johnson ---
Thanks, let me know if you need me to check anything here.
The problem has existed since at least gcc-12. Initially I thought the QEMU
q800 VM had run out of memory, but switching to a virt VM with ~3 GB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
--- Comment #4 from Stan Johnson ---
Adding more swap space doesn't help.
The latest Gentoo update attempted to merge gcc-13.1.1_p20230520, and it failed
while compiling gimple-match.cc in stage2.
The error message is "virtual memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109927
Bug ID: 109927
Summary: Bootstrap fails for m68k in stage2 compilation of
gimple-match.cc
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
