https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #41 from Brjd ---
(In reply to Sam James from comment #40)
> That came up at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600#c29.
IMHO keeping the build at RAM<=1GB would be a good benchmark. Keeping these
million-line files
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #40 from Sam James ---
That came up at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600#c29.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #39 from Brjd ---
Let me share what I notice in 14.1. Significant improvement in insn-emit.cc and
gimple-match.cc. This is good news.
Insn-recog.cc is much the same and needs ~ 1.6 GiB RAM. Yet, another possible
issue in the future
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Brjd changed:
What|Removed |Added
CC||brjd_epdjq36 at kygur dot com
--- Comment #38
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #37
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #36 from Brjd ---
I got memory troubles with insn-recog.cc and gimple-match.cc too. Please
correct them for gcc 10-13 in the their last .5 releases, so that we can
bootstrap.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
Sam James changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #34 from mmokrejs at gmail dot com ---
Thank you all. Just to clarify
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179#c31 , I did not show the Oom
error itself nor the cmd killed dut to that but you can see details at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #33 from Tamar Christina ---
(In reply to Sam James from comment #32)
> I'll tentatively reopen as IIRC tamar mentioned they've had some ideas about
> this, apologies if I'm misremembering.
Hello, yes I have a patch locally that I
